Why doesn't TextEdit text_changed signal send the new text as a parameter?

[MarcusElg]

LineEdit has the new text as a parameter when sending the text_changed signal which makes it easy to sync it with a variable, this however is not the case with TextEdit. Is there a reason for why? Wouldn't it make more sense for these two nodes to be consistent?

[Calinou]

Wouldn't this cause performance issues for very long TextEdits? Therefore, it makes sense for this to be opt-in (i.e. you have to get the text manually).

Edit: See also godotengine/godot#59818.

[Calinou]

It's uncommon for a LineEdit to have very long text, since it's single-line by design. In contrast, long TextEdits are quite common (e.g. code editors).

[MarcusElg]

Ok makes sense I guess, would be nice to have the option though.

[eon-s]

Maybe it can just send line and column of the changed text? there is another signal that does that.

[timothyqiu]

Strings are copy-on-write I believe, so I don't think it's related to text length. Text in LineEdit is a simple String, but text in TextEdit is an array of line info objects that each contains a String of that line. So it'll need to assemble a new String from that array if you want to receive text as parameter.

[MarcusElg]

Strings are copy-on-write I believe, so I don't think it's related to text length. Text in LineEdit is a simple String, but text in TextEdit is an array of line info objects that each contains a String of that line. So it'll need to assemble a new String from that array if you want to receive text as parameter.

Ah ok, that explains it