TIL that in TypeScript, if you define a class with readonly properties and an empty constructor, TypeScript will automatically assign the properties to the class.

Not sure if I love that, tbh, since I was under the impression that TS tends to not modify logic...

Same deal for `public name` / `private name` / `protected name`. Pretty sure they did it this way so you don’t have to repeat the same definitions in the class body.

Downside of this shorthand is you’re limited to using single ordered arguments in the constructor.

Staff Eng at Iron Fish • Building BlockSocks 🧦

Same deal for `public name` / `private name` / `protected name`. Pretty sure they did it this way so you don’t have to repeat the same definitions in the class body.

Downside of this shorthand is you’re limited to using single ordered arguments in the constructor.

https://www.typescriptlang.org/play/?#code/MYGwhgzhAEAqAWBLAdgc2gbwFAEhgHtkIAXAJwFdhj9SAKXHAB1P2IFMq2ATaMALmglSKVABoGjcgCMQiYNCkChI8TibCAbmHbRgSsitwBKTFlwBfLOaA

This isn't logic modification, as the `readonly` is only a part of TS's type system. There's no `readonly` in JS. So, stick your prev. assumptions on *logic modification* of TS.

/frontend dev・founder/decentralized data wrangler /blockhead・ritual.net・UI/UX abstractionist・DeFi/web3 builder・dropout・24・prev /dydx・x.com/darryl__yeo

I see no problem in it:

https://warpcast.com/behkod.eth/0xdc37f259