todo.sr.ht

repl:11:> (macex1 '(match token
repl:12:((>       (@ parser/Special {:value char}) (handle-special s char)
repl:13:((>       _ (eval/eval-and-push s token)))
(as-macro <function match> token {:_name "parser/Special" :value char} (handle-special s char) _ (eval/eval-and-push s token))
We are taking the name directly and using that in the pattern match. Instead, we should try to eval the symbol, get the name off of the actual table, and use that.

#9 Allow creation of prototypes inheriting from raw tables? 16 days ago

Comment by ~subsetpark on ~subsetpark/fugue

defproto call succeeds;
repl:7:> (:new Foo)
error: expected iterable type, got nil
  in new-from-Foo [repl] on line 3, column 1
  in _thunk [repl] (tailcall) on line 7, column 1
creation fails

#12 Don’t rely on prototype relations inside of meta 16 days ago

Comment by ~subsetpark on ~subsetpark/fugue

The only setproto calls are now when creating a new proto, or creating an instance.

REPORTED RESOLVED FIXED

#11 Enable nested with-slots 16 days ago

Comment by ~subsetpark on ~subsetpark/fugue

Fixed with with-slots-as

REPORTED RESOLVED FIXED

#13 `match` behaviour in multimethods heads? 16 days ago

Comment by ~subsetpark on ~subsetpark/fugue

I'd want the type-based arguments - :number/<Proto name> - to be the primary usecase. But that would be a powerful erlang-like advancement.

#13 `match` behaviour in multimethods heads? 16 days ago

Ticket created by ~subsetpark on ~subsetpark/fugue

For instance,

(defmulti f [(l (= 0 (length l)))] ...)

or

(defmulti f [{:key value}] ...)

#12 Don’t rely on prototype relations inside of meta 2 months ago

Ticket created by ~subsetpark on ~subsetpark/fugue

It will cause inconsistency if you end up changing the prototype of the object itself.

#10 Recurse when defining prototype-prefixed getters 2 months ago

on ~subsetpark/fugue

REPORTED RESOLVED WONT_FIX