dodexahedron
dodexahedron
Yep, I'm aware of that. I'm pointing out that, specifically, the C\# compiler doesn't emit good code for recursion, even though the relevant opcodes are available in IL. It's an...
Yes. It's not a question of accuracy. It's a notice of performance considerations due to implementation details of the C\# compiler and debugging difficulty, if an exception (of any kind...
> Cool, I've never used that Resharper feature. Didn't know it existed. > > I'll give it at try when I tackle this issue. Yeah it's pretty nifty. Though it...
> Normally when the stack overflow exception throw it's in situations where the values passed into parameters and the return values are always the same for about 1000 times, more...
Probably? 🤔 I guess if I notice anything still weird when I get back to stuff dependent on that, I'll file charges or whatever. 😛
The new title is concerning. Property getters are typically not supposed to throw exceptions unless there is a really really good reason for doing so. From the property design guidelines:...
> > The new title is concerning. > > Property getters are typically not supposed to throw exceptions unless there is a really really good reason for doing so. >...
> I implemented a POC: > > ```cs > case Pos.PosView posView: > if (posView.Target == SuperView) { > throw new InvalidOperationException (); > } > newLocation = pos?.Anchor (superviewDimension)...
Unless, of course, you intend to fix it now or otherwise before that.