Timeline for Hex string to Base64
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 2, 2017 at 18:02 | history | edited | Shepmaster | CC BY-SA 3.0 |
added 1 character in body
|
| Nov 2, 2017 at 18:00 | comment | added | Doug Bradshaw | Carmack's note at the top suggests that his major goal in inlining is avoiding surprise state changes. If he's talking about mutations in the parameter objects like I think he is, then I think Rust avoids the surprises by requiring mutation and ownership documentation. This obviates inlining, freeing you up to maintain a nicer separation of concerns. | |
| Nov 22, 2016 at 18:13 | vote | accept | sYnfo | ||
| Nov 22, 2016 at 0:24 | comment | added | Shepmaster | @sYnfo I've updated with responses. I don't really agree with Carmack, but I haven't made a AAA video game either. | |
| Nov 22, 2016 at 0:23 | history | edited | Shepmaster | CC BY-SA 3.0 |
added 559 characters in body
|
| Nov 21, 2016 at 19:57 | comment | added | sYnfo | Thank you! Great points. 2) Is there a better way to write debug statements? 3) That was me testing out number-none.com/blow/john_carmack_on_inlined_code.html, but since the function don't mutate state anyway, I do agree separate function are better 12) For whatever reason I thought that's would mean doing extra work, good to know it isn't. 13) I'm not sure what this one means? | |
| Nov 21, 2016 at 17:37 | history | answered | Shepmaster | CC BY-SA 3.0 |