blog post: signature polymorphic methods #1428
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
SethTisue
force-pushed
the
signature-polymorphic-methods
branch
from
4c46558
to
8a7f545
Compare
This comment was marked as outdated.
This comment was marked as outdated.
Co-authored-by: Sébastien Doeraene <sjrdoeraene@gmail.com>
Co-authored-by: Sébastien Doeraene <sjrdoeraene@gmail.com>
SethTisue
force-pushed
the
signature-polymorphic-methods
branch
from
ae6bab6
to
b6dfd59
Compare
|
I've handled all the review feedback and dealt with all the TODOs that I'd left for myself — either by addressing them or by deciding it didn't matter. I think this is ready to publish. I've set the publication date to Monday, July 17, 2023. At publication time I'll also make a forum thread on Contributors, and I'll fix the link at the end to point to it. I've left all the separate commits to aid review, but I'll squash-merge at publication time. |
|
anyone have any clue why the spurious "BLOG-DETAIL" at the top is there? I copied the header format from other blog posts, can't figure out what's different in mine. 
|
category: blog-detailas opposed to layout: blog-detail |
|
Thank you, Eugene! Somehow my eyes failed to see that. yup, 3de1d6e fixed it new URL of the post is https://scala-lang.org/2023/07/17/signature-polymorphic-methods.html now I need to figure out how to add a redirect from the old URL, which is now 404 |
|
redirect: f21a70d |
about 85% finished — still has a few holes and TODOs, but most of the material is therenot for immediate publication. I think a good time to publish it would be at the time the feature first becomes availablein Scala 3 (in an RC? or in a final release? I think an RC might be sufficient, and might get people to try it and report bugs in time)
(and it isn't clear yet whether the feature will have to wait for 3.3 or could land in 3.2.x, depending on whether we have to change TASTy or not)it's 3.3