Marek Kochanowicz
Marek Kochanowicz
Error caused by build problem in vellum itself. I've corrected this error just now.
I think that being strict on typing makes sense. However, here you would need to scan for the common type, and it seems to be complicated? Why even bother, either...
I am suggesting that everything should be assumed to be T, unless the explicit type is provided by the user (which is what CL ordinarily does in most places).
(1 . (2 3)) is the same as (1 2 3). Nothing wrong here.
Yes, you need to pass function. The other way to construct hamt is with make-from-traversable https://gist.github.com/sirherrbatka/d2134ae52da368d2216dde8ee668c006
I think that it is very useful tool for certain types of use cases, especially when combined with aggregation functions and stuff like that. For instance consider this example with...
Arrow macro is cool. But I am talking about functions in the cl-ds package. Without, array-elementwise, group-by and so one work by creating lazily evaluated streams.
Should we introduce another subclass for declaration specifer or just use expression-cst?
What I personally do is store those events in a buffer, and handle them after parsing the frame. I had to do this because of weapon fire events popping up...
The above stack trace was produced when i was trying to create a group chat.