-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Track demystified puzzlers #4553
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
A written source would be great. The only source I have seen discussing this specifically is the scala world talk on puzzlers Dotty would be resolving, as well as those for which a good solution has not been found like initialization order. https://youtu.be/Ay-9aanosUM |
A first step would be to add a list with checkboxes of all puzzlers to this issue, and start filling in their status. Any volunteer? |
I'll start by researching how to make a checkbox. |
|
@lihaoyi Scala Warts seem also relevant. |
@Blaisorblade thanks, some interesting conversations there. I meant to say that I mean to follow up on this meta ticket. First I need to understand how to make a table, so I can separate the puzzlers (intended behavior) from warts (behavior that seemed beautiful at the time, but is now only in the eye of the beholder). It really got under my skin when @lihaoyi brought up " |
I got started on this, but the first result was to create a new puzzler. |
I think #4831 also deserves to be listed as a puzzler. |
Closing for now, please reopen if anyone feel like going on a puzzle quest :) |
Since puzzlers.com is still live, it would be nice to know if any officially sanctioned puzzlers still obtain in Scala 3, since squashing them is a professed goal.
That is, the goal is to convert all puzzlers from "sanctioned" (approved as puzzlers) to "sanctioned" (banished from the language by decree).
The text was updated successfully, but these errors were encountered: