What is your evaluation of the proposal?
-0.5
Is the problem being addressed significant enough to warrant a change to Swift?
It's a useful method, and I wouldn't hesitate to include compactMapValues in a dedicated collection-library... but when we talk about Swift itself, I don't think it fulfills the requirements:
A method name that consists of more than two words imho is already a good indicator that a functionality isn't really fundamental, and as others pointed out before (Add compactMapValues to Dictionary - #11 by Jon_Hull), the implementation is quite obvious when you are not married to the idea of using fp exclusively.
Of course, including compactMapValues in the stdlib wouldn't hurt anyone... but there has to be a higher bar when we want to keep the stdlib lean (although I'm not sure if that is an official goal).
How much effort did you put into your review? A glance, a quick reading, or an in-depth study?
Read the discussion