Conversation
|
|
||
| ;; send the client response, whether success or failure | ||
| (%push-raw-request receiver identity empty-frame (serialize reply))))) | ||
| (handler-case |
There was a problem hiding this comment.
Emacs reindented this for me, but the real change is the handler-bind and the :|warnings| slot initializers.
9b4986e to
ffcb9b1
Compare
stylewarning
left a comment
There was a problem hiding this comment.
A few small things; looks fine overall.
|
|
||
| (defmethod %serialize ((payload cons)) | ||
| (loop :for elt :in payload :collect (%serialize elt))) | ||
| (map 'vector #'%serialize payload)) |
There was a problem hiding this comment.
can we nix serializing conses altogether?
There was a problem hiding this comment.
If you were to ask me: yes. If you were to ask someone else with more principles about backwards compatibility: no, or not yet.
|
|
||
| (defmethod %deserialize ((payload cons)) | ||
| (loop :for elt :in payload :collect (%deserialize elt))) | ||
| (map 'vector #'%deserialize payload)) |
3e3d16a to
184e414
Compare
|
This LGTM. What changes ripple through the stack? |
|
AFAICT, this is the only ripple: quil-lang/quilc#188 . |
|
let's merge after the weekend |
|
Weekend is done; anybody want to merge? (I'm not a CODEOWNER.) |
|
Only serious concern is whether this will swallow warnings in the server logs. |
|
ty everyone |
Closes #43: captures Server-side warnings and re-raises them on the Client side.