P4
A DESCRIPTION OF THE PROBLEM :
I would like to give my feedback to the upcoming StableValue/LazyConstant features, by just mentioning to keep the simple generic naming of this to just `Lazy` instead of having `LazyConstant`. I feel like this would be much more simpler and nicer to be aligned with other core apis (e.g: Stream or Optional), that are named with just one word which also looks simpler.
If this would be rejected, then I would have a question: Why would this class needs to have a description in its name about being something constant or something that represents immutability? As of course it can be immutable after its initialization as it was described in the previous jeps.
I would like to give my feedback to the upcoming StableValue/LazyConstant features, by just mentioning to keep the simple generic naming of this to just `Lazy` instead of having `LazyConstant`. I feel like this would be much more simpler and nicer to be aligned with other core apis (e.g: Stream or Optional), that are named with just one word which also looks simpler.
If this would be rejected, then I would have a question: Why would this class needs to have a description in its name about being something constant or something that represents immutability? As of course it can be immutable after its initialization as it was described in the previous jeps.