They refuse to compromise even on documentation issues. I am totally helpless. Not sure what could be done?
On Sat, Dec 3, 2022 at 2:48 PM Marco Pivetta <ocram...@gmail.com> wrote: > Talk to the designers then: bringing your own political issues up to the > programming language/tooling only makes it worse long-term, for everyone 😛 > > On Sat, 3 Dec 2022, 23:45 Karoly Negyesi, <kar...@negyesi.net> wrote: > >> I do not have the luxury of designing my own system. I am forced to use >> upstream. I can't help it and given the history of private usage and the >> refusal on relaxing them I do not see this improving with the readonly. At >> all. >> >> On Sat, Dec 3, 2022 at 2:42 PM Marco Pivetta <ocram...@gmail.com> wrote: >> >>> Terrible idea: reflection is mostly introspection tooling, and doesn't >>> really bend the rules of the type system, other than crossing scope (it >>> "sees" more). >>> >>> Please consider designing your system to consider the constraints of >>> `readonly` properties, or design the constraints to fit your system instead. >>> >>> Marco Pivetta >>> >>> https://twitter.com/Ocramius >>> >>> https://ocramius.github.io/ >>> >>> >>> On Sat, 3 Dec 2022 at 23:39, Karoly Negyesi <kar...@negyesi.net> wrote: >>> >>>> Hello, >>>> >>>> If push comes to shove, private properties can be changed with >>>> reflection. >>>> >>>> Readonly properties can't. >>>> >>>> Please add a readonly toggle to reflection. >>>> >>>> Thanks >>>> >>>> Karoly Negyesi >>>> >>>
