Luke Champine

It's possible that your wallets are desynchronized. Try using the tool I created here: https://github.com/NebulousLabs/Sia-UI/issues/581#issuecomment-299747969

Actually you got it right the first time, this is a Sia issue :P This panic comes from the database. Can you try deleting the existing folder and resyncing the...

Is your node fully synchronized? You won't see any coins in your wallet until you have downloaded the entire blockchain, which takes a while. Unfortunately the block explorer isn't super...

I think we discussed empty folders awhile ago and came to the same conclusions you did: either you fake it locally, or you eat the cost of uploading invisible metadata....

This would be cleaner if Go had a standard compression interface, like a `compress.Deflater(io.Reader) io.Reader`. Then you could just pass in a `compress.Deflater` to the update and it would handle...

As an addendum to the last paragraph: It may be possible to design a lambda syntax that is still legal Go, at least as far as the parser is aware....

I realized a second later that boolean XOR is just `!=`. Oops. Boolean assignment operators would still be nice though.

~Three~ Four more potential solutions: - Provide separate functions that can reuse memory, e.g. `rfilter`, `rmorph`, etc. This is easiest to implement on the backend, but I don't like the...

Another potential solution: immutable slices. If we introduce an `immutable` builtin (or keyword), then this optimization may simply "fall out" as a consequence. For example, this code would always allocate...

Another potential solution: a `dup` function. Like so: ```go xs = xs.filter(even) // reuses memory xs = dup(xs).filter(even) // doesn't ``` I like this because it makes the cost explicit....