You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have noticed that Xtend does not use Java multi-line strings for Xtend multi-line strings, even if Java 17 is the target version.
This incurs in an overhead because strings which could be constants need to be constructed at runtime, which can as well created duplicated strings, even if the resulting string is always the same.
Have I missed some configuration option or is this not implemented? If so, any plans on implementing it?
The text was updated successfully, but these errors were encountered:
That's something I had in mind to work on if @szarnekow thinks it's worthwhile. I've always forgotten to open an issue, though.
Note however that a direct translation into text blocks (I think that's what you meant) is not always possible I guess, especially in the presence of nested if and loops.
Moreover, Java text blocks always end with \n, while Xtend template strings use the OS' end of line, so that's something we should discuss first, I guess.
Note however that a direct translation into text blocks (I think that's what you meant) is not always possible I guess, especially in the presence of nested if and loops.
Yes, that what I meant, thanks.
What is the problem with nested if and loops if the text block is constant?
I have noticed that Xtend does not use Java multi-line strings for Xtend multi-line strings, even if Java 17 is the target version.
This incurs in an overhead because strings which could be constants need to be constructed at runtime, which can as well created duplicated strings, even if the resulting string is always the same.
Have I missed some configuration option or is this not implemented? If so, any plans on implementing it?
The text was updated successfully, but these errors were encountered: