An official solution for crowded namespaces (modules, packages, conventions, &c.)
tel
|
cached 6 days ago
|
|
cached 23 days ago
Any chance we can get some official word on concerns about namespace clashing?
|
|
cached 11 days ago
Lose the text inside the logo.
I love the rotating arc, but simplicity is king when you're aiming at a brand. |
|
cached 9 days ago
It's not a popular idea in lisps, but set terminology, "list comprehensions", would be an interesting thing to see.
Of course, if you're going to do that, {} is probably the logical choice...
|
|
cached 23 days ago
Seconding on the module system. It may not be the biggest concern of a young language, but it's a big part of the infrastructure that will let the language grow.
|
|
cached 13 days ago
Haskell chooses this order because partial application and pointfree style are really common.
But since partial application is not a default behavior in Arc ([map square] and [map _ square] are not that different from one another) the order of the fn and list aren't as important.Rule of thumb might be: put the fastest changing piece last, but this syntax thing might be a stronger heuristic. |
|
cached 13 days ago
Well, pg has at least suggested that he will add that functionality. This is the first I've seen of this presymbol operator.
If you can't wait, implement this or presymbol syntax into Anarki. |
|
cached 3 days ago
Of course, that means that any designer has to be fluent in Arc's libraries as well.
Not to suggest that Arc's method is anything short of perfect for what Arc does, but a big benefit of MVC is how separation of logic and presentation reflects separation in personnel. |
|
cached about 22 hours ago
I definitely understand the desire to optimize...
... but doesn't this seem like a pretty quintessential example of premature optimization? |
|
cached 13 days ago
|
