4 ms·
~1.5 years ago, we did a project in Groovy and found that some things were not quite there, like passing named parameters into a constructor.
by pyre 15y ago
~1.5 years ago, we did a project in Groovy and found that some things were not quite there, like passing named parameters into a constructor.
- mgkimsal 15y agoDid you submit a bug report? I'd be curious to see what you were doing that caused a problem. I've been using Groovy for > 3 years and haven't hit an issue with named parameters, but I might be using just simplified cases compared to you.
- pyre 15y agoI think that we just gave up on it. Another thing that I remember being really annoying is that there was no easy way to break out of iterating closures other than to throw an exception. I ended up writing a "BreakClosure" exception specifically for this. (The return value of the closure goes nowhere, and breaking out of one closure just causes the next iteration to run.)
- mgkimsal 15y agoAgreed on breaking - hadn't thought of that approach. I'm used to 'continue/break' from PHP, so reworking the iteration loops to check if the loop should run is annoying. :/ Maybe I'll try your exceptional approach too.
- deleted 15y ago[deleted]