> If a class can't work within these constraints, then it can declare the variable as Option<T> initialized to None, and then it is back ...
> If a class can't work within these constraints, then it can declare the variable as Option<T> initialized to None, and then it is back to the normal Java semantics for that one variable. By doing that you lose the safety of variables being marked final. I wish there was a way to seal a variable such that it could not be changed (in the same sense that final works in, not truly readonly) after a certain point, but it could be before then. I find myself writing far too many variables that should be final, and indeed are final after a certain point, but cannot be marked as such because said point is after the constructor. In particular with lazy-loading.
Posted by TheLoneWolfling on May 28, 2015, 5:38 PM
Tags
Related issues
- I wish there was a way to sort by recency, if i'm mainly interested in finding obscure gems from like last 6 to 12 months of ai and tech ...
- Android work profiles allow you to run multiple isolated copies in parallel - with separate address book and all.
- The other day I saw the last episodes of The Office again.
- > someone has made the wrong editor choice Just the other day I made this comment on the topic of "nvim vs emacs", I think it fits here ...
- GLES isn't a bad way to teach graphics but I wish there was a middle ground between it and VK.
- > [Edit: note that the above video is "content" so if you're not used to the style it might be offputting but I'm into it] I hate that i...
Raise real-world problems, find people facing the same issue, and discuss solutions.6,500 issues0 comments
complaint (Other)
I wish there was a way to sort by recency, if i'm mainly interested in finding obscure gems from like last 6 to 12 months of ai and tech ...
NewAndroid work profiles allow you to run multiple isolated copies in parallel - with separate address book and all.
NewThe other day I saw the last episodes of The Office again.
New> someone has made the wrong editor choice Just the other day I made this comment on the topic of "nvim vs emacs", I think it fits here ...
NewGLES isn't a bad way to teach graphics but I wish there was a middle ground between it and VK.
> [Edit: note that the above video is "content" so if you're not used to the style it might be offputting but I'm into it] I hate that i...
And thats why its a large language model not a large skin cancer recognition model or large creative thinking model I hate that people th...
I hate that this article is talking about Photocraft killing Photoshop because of AI as though Ivan Kutskir didn't build Photopea years a...
> If a class can't work within these constraints, then it can declare the variable as Option<T> initialized to None, and then it is back ...
> If a class can't work within these constraints, then it can declare the variable as Option<T> initialized to None, and then it is back to the normal Java semantics for that one variable. By doing that you lose the safety of variables being marked final. I wish there was a way to seal a variable such that it could not be changed (in the same sense that final works in, not truly readonly) after a certain point, but it could be before then. I find myself writing far too many variables that should be final, and indeed are final after a certain point, but cannot be marked as such because said point is after the constructor. In particular with lazy-loading.
Comments (0)
No comments yet. Start the discussion.