Closed spy16 closed 4 years ago
@lthibault Thoughts?
Two general thoughts:
(/ 21 19)
. When this happens, we should revisit the assert
function to handle floating-point errors. I think it's fine for now, though.makeContainer
and containerString
in a utility package (e.g. sabre/util/container
) ? I'd like to reuse this logic in wetware.Other than that, 👍. Looks like the beginnings of a nice little standard library !
Not a big fan of utility packages because they have a tendency to be a dumping ground. And also not a fan of exposing things unless they are very generic and necessary to be exposed..
That said, I do have plans to create a generic version of type initialization. sabre.Type
type is invokable. And my idea is to use this invocation to enable initialization of that type. When that is done, makeContainer
will be removed. Also, when this is done many of the type init functions and type check functions will be removed from go code and added as pure lisp code (vector
, vector?
etc.)
Adds tests for slang using lisp files in
./examples
directory