Isak Sky

> if-let and if-some are not clauses to be used within cond. They are standalone macros that can be used in place of the built-in if-let and if-some if you...

@Engelberg I understand - appreciate the the explanation!

@leebyron For cases where you know the object you would like to mutate, but don't know what cutesy name your colleagues decided to give the mutation (updateStory, changeStory, likeStory), I...

Regarding "namespaces only required if there is a collision": that is an extremely dangerous semantic, because it means adding a field can break queries, which I expect most people will...

I think this, as well as adding normal imperative "return" would be a great change to F#. Right now in F# there are a few alternatives: 1. Increase nesting (if...

Have you considered just not trying to convert it? This would arguably be better, because then users can do it themselves if they have a working way to do it.

He fixed it with this commit: https://github.com/isaksky/transit-erlang/commit/4c43bd03d06d2303e0b5fecfc7244395161639c7

How I imagined it would work is roughly like this:  So if you click on the deref, everything from there on out would be refreshed. I'll think about those...

@cartermp 1. In some cases now there is ambiguity from guessing the type the user is trying to construct based only on the field names. For example, imagine if you...

@Rickasaurus I've seen that, and I think for the former, the problem is it may be far away from the actual `{...}` syntax at the end of the expression, which...