Lack of property accessors (get, set)

[KnightBreaker]

Verse still lacks of getter and setter accessors.

While the intended future design is unclear, it is desired not to require fully named and re-routed getter setter methods as it just adds unnecessary boiler plate code that the library author would like to hide from the library users.

Not desired example:

var Value<getter(GetValue)><setter(SetValue)>: int

GetValue<private>()<reads>: int = { ... }
SetValue<private>(Value: int)<transacts>: void = { ... }

Desired example:

# read/write property
var Value: int = {
  get { 
     ...
  }
  set {
     ...
  }
}

# read only property
var OtherValue: int = {
  # `get { ... }` is inferred
}

[janvitek]

My understanding is that this will not be supported.

[KnightBreaker]

Isn't epic using getter/setter already? So why would that feature be only for Epic?

[janvitek]

There is some feature yes, but it is limited and I know that it not the way the language is planned to go.

This said I have not seen any documentation/spec and the discussion about this pre-date me.