It’s not just “Some Completion”, it’s about scala.Some.
In case if you have expected type Option[AnyType] you possibly have something of type AnyType and you want to use it like Some(anyTypeValue). So now you can invoke smart completion two times and you will see such possibilities
And then you will get
I love the title of this post (and its content of course).
I come from Newfoundland where its not uncommon to hear “He’s some smart b’y” which means “He’s very smart” in our local dialect.
This is a great feature that lowers the client-code authoring cost of using Option. Minimal though it may be it definitely has a cognitive friction that this feature basically totally removes.
Thank you