4 ms·
Yes, the general idea is not new but the devil is in the details. As far as I can tell, Odin's `using` is applicable in the same areas as Kotlin's, but I still
by hota_mazi 7y ago
Yes, the general idea is not new but the devil is in the details.
As far as I can tell, Odin's `using` is applicable in the same areas as Kotlin's, but I still favor Kotlin's scoped version. When I see "using foo;" in Odin, it's not quite obvious to me where the scope of applicability is.
Any reason why you didn't do something like
entity.use {
// "this" is now the entity instance
}
// back to your regular "this"
?
- gingerBill 7y agoYou can easily do the same in Odin, if you would like. However, `using` works for a lot more than that just this. `using` allows for many for type system features beyond a basic scope import like Pascal's with. `using` can be applied to procedure parameters, struct field declarations allow for subtype polymorphism (even of pointers), scope imports, and more. Koltin's approach is limited to purely the same Pascal's `with` allowed. But if you want to be clear: { using entity; // the fields of "entity" are not usable in this scope x = 123; } entity.x = 123;
- gingerBill 7y ago* are now usable typo