switch prong captures may no longer all be discarded
What does this mean? Which ones? Does “all” belong to “switch prong captures”, or to “discarded”?
Incremental compilation sounds fun, but my builds are already near instant 
Really excited by all of the implicit coercion! Now the trick will be figuring out which instances of @floatFromInt, @intFromFloat, etc. are no longer needed in my codebase…
“all” applies because you can have multiple catptures when switching on a tagged union |payload, tag|. if both are discarded |_, _|, or in the case of a single capture |_|, it is no different than not having the capture at all. So they decided not having it at all is the preferable syntax, and made discarding all captures an error
3 Likes
Ah, that’s fine then. Assuming I can still ‘park’ a capture the old fashioned way with _ = cap; // TODO and I must assume I can.
Switch captures were the odd ones out, since other captures are syntactically required. This makes sense to me. (Now that you’ve explained it, that is; the release note admits of some improvement in clarity, IMHO).
Congrats and thanks to the contributors for their hard work on 0.16.0