Fork me on GitHub
#portkey
<
2018-05-28
>
cgrand14:05:09

> `“Fonction tu lui donne un input et il t’appelle les fn de ser qui on été généré pour faire le confirming.“`

cgrand14:05:01

Guys, if we start writing comments in our own languages this codebase is going to be fun

baptiste-from-paris14:05:31

ahah, it was dev stuff only

cgrand14:05:01

Kidding, the worst is if it hasn’t been written in Frenglish I may have failed to notice it

cgrand14:05:14

On the generated side: it should be more straightforward (no iteration or lookup not related to the data). On the generator side: what are the gains of a single omniprotocol multimethod (opposed to eg a multi per protocol)? Last on resp and one-per-protocol: maybe but I have the same feeling/doubt that about gen-ser-input: that we are prematurely factoring things together with little gain.

cgrand14:05:34

Do you see what I mean? Maybe I’m missing something

baptiste-from-paris14:05:03

I understand your last point but not the first 2 🙂

baptiste-from-paris14:05:13

1) generated code is to complex ?

baptiste-from-paris14:05:20

2) interface is not the right one ?

cgrand15:05:44

on point 2: is there any reason (other than making code similar across protocols) for having a single multimethod for all?

cgrand15:05:15

on point 1: how would you write ser-tracing-config by hand?