mdedetrich commented on issue #362:
URL: 
https://github.com/apache/incubator-pekko/issues/362#issuecomment-1568671027

   Okay so I had a proper look into this including other converter functions 
which are not explicitly mentioned in this issue (I think its useful to tackle 
this properly at once)
   
   * `FutureConverters`: This shouldn't require any adjustment to 
`LICENSE`/`NOTICE`/headers because there is no copied code, its just a wrapper 
that forwards function calls to the actual implementation which is a standard 
jar dependency
   * `OptionConverters`: This is the same as `FutureConverters` but there is 
one "technically" correct exception which is 
https://github.com/apache/incubator-pekko/blob/898c69701b7783e6da9e69321ca345ea98ddc86b/actor/src/main/scala-2.12/org/apache/pekko/util/OptionConverters.scala#L28-L37.
 The reason why I state this is "technically" correct is that while its true 
that the code is the same (not exactly lexically but the compiled meaning of 
the code is the same) its basically impossible to come up with an alternative 
implementation since its so trivial (to drive this point further, this is about 
as trivial as asking someone how to add two numbers, 99% of people would write 
it as `a + b`). IANAL statement here, I am not going to make a call whether we 
should make a legal understanding of this, I just want to be clear about how 
benign/trivial the code is.
   * `FunctionConverters`: Same as `FutureConverters`, its just forwarder 
functions, i.e. no copying of code.
   * `ccompat` ergo collection compat: This is the one area where code was 
literally copied from `scala-collections-compat`. I guess that due to this we 
should should also copy the header over (i.e. 
https://github.com/scala/scala-collection-compat/blob/main/compat/src/main/scala-2.11_2.12/scala/collection/compat/BuildFrom.scala#L1-L11)
 and mention it in `LICENSE`/`NOTICE`.
   
   @pjfanning Let me know if this answers your questions


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to