George Marques

They were closed long ago. These are the two I got yesterday: - https://github.com/godotengine/godot/issues/9335 - https://github.com/godotengine/godot/issues/9744

I also have this problem. I'm using `src` folder for the sources and `include` for the headers. From `include/parser.hpp` it correctly open the source file, but from `parser.cpp` it opens...

I bumped into the same issue. It seem this is already fixed but haven´t made into a new release yet. See: https://github.com/containers/podman-compose/issues/406#issuecomment-1015256254

I believe this is fixed already, the mentioned error message does not even exist anymore (probably became not relevant).

I cannot reproduce. There has been many changes since the report, so I'll assume it was fixed along the way.

> Also, we should not forget about readonly `Packed*Array`s (`make_read_only()`), for consistency with `Array` and `Dictionary`. This might be tricky because `Packed*Array` are just `typedef`s for `Vector`. Adding read-only functionality...

> Updated PR to allow inference of hard Variants for variables: > > ```gdscript > var var_i := variant() # error -> safe > ``` I'm not sure if this...

> Sorry, but I don't understand what problem this solves. One of the big things in Godot 4.0 was the lesser reliance of strings (mostly signals and methods, which now...

PS: About `@rpc`, ideally they would be an enum value. But creating an enum for this would be redundant, and using `MultiplayerPeer.TRANSFER_MODE_UNRELIABLE` would be quite annoying. Similar for `@warning_ignore`. Annotations...

The benefit is cosmetic but I believe it's a benefit nevertheless. Consistency is not that important, especially not in detriment of other improvements. As an illustration:  Having `CustomNode` highlighted...