Meeting to discuss Magnolia's future #241
Comments
|
interested :) |
|
me too |
|
interested as well. |
|
Interested! |
|
Me too :) |
|
+moi :) |
|
interested |
|
Interested for sure count me in Sir |
|
Interested, thanks |
|
Not really certain whats at stake, but yes, nice. An interested observer. |
|
I would love to attend. I toyed with adding support for alternative "helper" typeclasses but it was adding too much complexity. |
|
Count me in |
|
Interested. |
|
Wouldn't have time for a full meeting, so I'd just say the exact thing I'd say on the meeting anyway: we need a dotty support module to ease Scala 3 migration – either a full reimplementation of Magnolia for Scala 3 or a proxy over |
|
interested! Thanks |
|
interested in contributing, thx |
|
Thanks for replying everyone! I've sent everyone* three calendar invitations for meetings on three days next week. (Tuesday, Wednesday, Thursday evenings, in Europe at least.) Please accept all of the times that you could potentially attend. I will remove two of the options on Sunday so that by the start of next week we will have settled on a date/time. * If you didn't get the invitation, it's because I have the wrong or no email address for you! Please send me a Twitter DM to |
|
As one of the outputs, we decided to have someone try using getting Magnolia to provide a high-level API over Scala 3's typeclass derivation - I tried the new derivation mechanism yesterday and would like to take on this challenge (at least to identify any major roadblocks) sometime soon. :) |
|
Awesome, let's have a chat about it some time! |
|
I'm going to close this issue before it becomes a general discussion area... |
Agenda
furybranch the defaultPlease leave a note here if you would be interested in taking part in the meeting. It would help if you could DM your email address to
@propensivein advance so I can send you a calendar invitation.The text was updated successfully, but these errors were encountered: