Hi, I noticed an important issue in lambda referen...

# announcements

[louiscad]

Hi, I noticed an important issue in lambda references which are supposed to be equivalent to their lambda counterpart: they use the reference of the object on which they are applied, and not the reference member. It means that when I update my member property, the old value is still used to execute the method reference while the new one is used if I use a lambda instead.

Anyone from JetBrains to help me clarify if this is the expected behaviour?