Re:Pony: An actor-model, capabilities-secure, high-performan...
by shiomiru on Tuesday July 29, 2025 @03:45PM
(#44727492)
Nim's import rules are part of its generalization of OOP's obj.foo()
syntax. That is, in Nim, you don't have to put "foo" in a specific
class, just set the first parameter of "foo" to the type of "obj",
and this only works if you don't have to qualify "foo" (similarly to OOP
languages...)
[ Parent
| on HN ]
Re:Pony: An actor-model, capabilities-secure, high-performan...
by maleldil on Wednesday July 30, 2025 @12:07PM
(#44736018)
I don't see how Nim's import is necessary for that to happen. You can allow the user to specify items to import without the qualifier (like Python's `from lib import foo`), and the universal function call syntax would work, too.
Re:Pony: An actor-model, capabilities-secure, high-performan...
by shiomiru on Wednesday July 30, 2025 @01:08PM
(#44736772)
That is allowed, with the exact same syntax as Python. But then you still lose the qualification so I don't see any benefits, it's just more boilerplate to constantly adjust, git conflicts to fight with, etc.