3 ms·
Leave less undefined in the specification. In particular, there should be more defined cases for errors in safe code. Complex type upgrading is just broken.
by pfdietz 4y ago
Leave less undefined in the specification. In particular, there should be more defined cases for errors in safe code.
Complex type upgrading is just broken. The spec is inconsistent.
sort should have been called nsort, to be consistent with the names of other potentially side-effecting operations. SORT would not alter its argument.
If defpackage has no :use clause, it would be equivalent to (:use), not implementation-defined. Also: make package local nicknames part of the standard.
Many built ins functions should be generic and allow user defined methods if at least one argument is not of a standard-defined class. This should not have an efficiency penalty.
Many built-in classes should be user extensible, or at least have internal generic functions that can be extended. The exemplar here is user defined sequences in SBCL. This would also be useful for hash tables and streams.
Pathnames tried to be general and failed. They need a revamp.
Add support for multiple threads, concurrency, unicode.
Although it saddens me to say it, get rid of the punning of NIL and false, and make CAR/CDR not work on NIL.
Although it's not part of the standard, have a more robust social mechanism for curating and maintaining a semi-standard library, just outside the standard.
Packages should allow weakness, so that if a weak symbol is not used anywhere it can be GCed from the package. This could help with tree shaking.
- deleted 4y ago[deleted]
- sargstuff 4y ago> Add support for multiple threads, concurrency, .. technically, already have that via lisp's take on decorators/generators. [1] What lisp doesn't have, per pre-dating just about everything in CS, is way to associate the lisp take on threads/concurrency with underlying os/hardware (without modifying/recompliling language). what would be nice is an alternate REPL namespace that can be 'reloaded to garbage collect, independent of standard REPL' where things that are split between OS/REPL/card reader operator can be placed. aka device drivers, thread/cpu/gpu specs. aka erlang/elixir extention ---- [1] : https://stackoverflow.com/questions/32956033/is-there-a-straightforward-lisp-equivalent-of-pythons-generators https://stackoverflow.com/questions/32956033/is-there-a-stra...