GDScript 2.0: assert() containing line breaks results in an syntax error

[ydipeepo]

Godot version

v4.0.beta1.official [20d6672]

System information

It's not system specific error.

Issue description

Any condition containing newlines in assert's () will result in a syntax (grammatical?) error.

Steps to reproduce

assert(
    true or
    true) # It raises "Expected expression to assert." at edit time.

But. Its works with \:

assert( \
    true or \
    true)

assert(
    true) # error

Minimal reproduction project

Include line breaks in assert expression.

[TheDuriel]

This is correct? You can't do this in any other context either.

[ydipeepo]

@TheDuriel Idk but I was wondering if it was allowed cuz it was possible in 3.5.
I hitted this problem when porting my addons.

Normal calls allow line breaks like this:

my_func(
    "text",
    1234,
    true
)

[TheDuriel]

What's letting you do that there, is the comma "escaping the linebreak".

assert(
    true or false)

assert(
    true or \
    false)

Should work.

OR and other operators require your code to continue on the same line.

[ydipeepo]

Yup, I know. Is it okay to recognize that it has become stricter?

[TheDuriel]

I'm not convinced from your example that is has.

[ydipeepo]

I checked it again.
It seems that line breaks between operands are not allowed in this version at the or / and, binary and unary operators in any function call arguments.
I don't know if it's a bug or a lang spec change, but I was able to deal with it like this:

assert((
    1 +
    1
)) # works

ceil(
    0.0) # OK
assert(
    true) # Error

[TheDuriel]

It'd be nice if you could do exact comparisons between 3.x and 4.x for this. With normal function calls and asserts.

[ydipeepo]

Sorry, I looked further and it seems that regardless of the operator, simply cannot break a line.

#66535 (comment)

[hsandt]

To complete use cases, I had this issue when splitting my long assert message over multiple lines:

	assert(is_on_floor(), "_get_floor_tangent: is_on_floor() is true yet get_floor_normal() " +
		"returned Vector2.ZERO.")

Replacing assert with a condition + push_warning for instance, will work.

[adamscott]

I confirm this issue on master (fcba87e).

Minimal reproduction project

66535.zip