Dave Thomas
Dave Thomas
Basically this: https://github.com/ctaggart/froto/blob/ba4d5e506e1be6105dc6746a08a1d6714793e8fe/TypeProvider/Core/Message.fs#L10-L19 Becomes an interface defined in Froto.Serialzation
The Message implementation can still live in `froto/TypeProvider/Core/Message.fs` just it implements the interface, then other code generators have a point or reference implementation.
Any thoughts @ctaggart / @jhugard
Basically I just want that interface in the first comment to be defined here.
The interface I suggested was based on what's implied via the srtp method constraints. On Fri, 31 Aug 2018 13:57 James Hugard, wrote: > Sounds quite reasonable. Should IMessage also...
So, are import statements currently processed, or was then never completed? cc @jhugard @ctaggart
It might be a good idea, or you might just be adding complexity to remove later on... I meant theres already quite a few hurdles and hoops to jump through...
I almost never use symbolics as I like to have the option of intellisense. When you come back to code you have written previously its really annoying to not be...
@mausch I think so, they seen sensible to me.
@mausch I know they wont be as pretty as infix symbolics, its a pity we don't have infix function declarations.