Pointers for getting a SIP through:
-
check the mailing lists to see what people might have said in the past about this feature - often a topic has been covered many times, and there’s lots of useful information, and I would bet this feature is the same
-
try and implement it, particularly given @odersky said it does not look that hard to do
-
when you write your SIP try your best to think up all feature interactions. This will help reduce iterations with the committee. A few examples off the top of my head: varargs, implicit argument lists, and using the same feature also for type members (eg.
def f(x: A, y: x.B)) -
there is an interest of this for implicits, currently worked around with the Aux pattern, and I believe there is a SI ticket / pending PR to introduce multiple implicit argument lists as an alternative workaround. Ultimately this feature super-seed both of those, imho.
-
when you respond to the SIP’s request for feedback, make sure that that feedback is very clear and not too “wordy” - for instance I’ve found the committee responds better to succinct lists over wordy paragraphs
-
work closely with your SIP sponsor, making sure he/she understands what you’re saying and/or asking, and making sure you understand what the committee wants from you and your SIP