-
Felix Lange authored
...and make it a top-level function instead. The original idea behind having EncodeMsg in the interface was that implementations might be able to encode RLP data to their underlying writer directly instead of buffering the encoded data. The encoder will buffer anyway, so that doesn't matter anymore. Given the recent problems with EncodeMsg (copy-pasted implementation bug) I'd rather implement once, correctly.
eb0e7b1b
| Name |
Last commit
|
Last update |
|---|---|---|
| _data | ||
| cmd | ||
| compression/rle | ||
| core | ||
| crypto | ||
| eth | ||
| ethdb | ||
| ethutil | ||
| event | ||
| javascript | ||
| logger | ||
| miner | ||
| p2p | ||
| pow | ||
| ptrie | ||
| rlp | ||
| rpc | ||
| state | ||
| tests | ||
| trie | ||
| types | ||
| ui | ||
| vm | ||
| websocket | ||
| whisper | ||
| xeth | ||
| .gitignore | ||
| .gitmodules | ||
| .travis.yml | ||
| Dockerfile | ||
| LICENSE | ||
| README.md | ||
| gocoverage.sh | ||
| install.sh |