Int * CSizefor example to pass to malloc. We are pretty used to being able to add an
longand having the result promoted to a
longat least in Scala. Promotion is pretty safe. Of course using unsigned arithmetic is safe if you want to avoid a negative number but the current ergonomics are quite cumbersome. This was the ngram processing which is easy to port but with the new changes I can't get it to work yet - not for this reason but another one.
@WojciechMazur A question, if you please, about handling & respecting Intellectual Property for PRs where the original author is unavailable. PR #1921 adds network datagram (UDP) support to posixlib. The conceptual content certainly Looks Good to Me. The exact textual content needs a rebase because of a later, merged PR which made the case of constants consistent.
It would be nice to do the rebase so that the person doing the merge did not have to do so. Would it be in line with
Scala Native's Intellectual Property guidelines for me to create a new PR, based on and acknowledging PR #1921, and do the rebase? Is there a better way to proceed? I am trying to help a community generated PR get merged rather than create stress. Thank you for your providing direction.
@Mergifyio rebasein a PR comment and it will rebase it
Would it be in line with
Scala Native's Intellectual Property guidelines for me to create a new PR, based on and acknowledging PR #1921, and do the rebase?
I have no idea how to minimise this test to something that I can share. So, if anyone have any ideas I'd love to hear it.
Handle[T]to be honest, just some based trial that manage everything.