Fabrizio Montesi
Fabrizio Montesi
Notice that with is typically problematic, like in javascript where they don't recommend using it: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/with So we might want to make some radical change here. We should identify in...
An example of a non-problematic with syntax: ``` with( my.long.path as a ) { a.x = 2 a.y = 3 } ``` :-)
Yeah, that's the easy implementation solution.
@jolie/developers Removing the bug label, per the discussion above. If anybody wants to take a shot at implementing `with( path as x ) { ... }`, please self-assign this.
Not a bug, technically, but it's so bad that I'm against tagging it as such. It should also be marked as enhancement, since it does not have a reasonable fix...
@jolie/developers, @klag and I had a chat about using .. to disambiguate with. ```jolie with(x) { ..y = 3 // this now assigns x.y = 3 } ``` This would...
Hi Balint, I think that a good starting point is proposing the flags for controlling the output, like getting the "verbose" error messages or the json format. Then, we need...
@oxxford: Thanks for the doc! @bmaschio: definitely. @oxxford and @bmaschio : Please try to think about suggestions/descriptions too when we encounter an error. I'm not 100% convinced we can give...
OK for me, but what about @oxxford . @lsafina what's the status on this?
Hi Balint, Thanks for starting this! This kinda inspired me: shouldn't we make *all* log messages configurable like this? Currently all log messages (errors, warnings, etc.) by the interpreter are...