On 2/2/2017 8:44 AM, Chris Wright wrote:
Assuming you're writing cross-platform code. How common is that?
Exactly. That's why Valgrind is not a substitute for a language that offers memory safety features.
Re: memcpy() comparison: C, Rust, and D
Walter Bright via Digitalmars-d Thu, 02 Feb 2017 12:57:55 -0800
- Re: memcpy() compariso... Richard Delorme via Digitalmars-d
- Re: memcpy() comp... Patrick Schluter via Digitalmars-d
- Re: memcpy() ... Chris Wright via Digitalmars-d
- Re: memcpy() ... Walter Bright via Digitalmars-d
- Re: memcpy() ... Richard Delorme via Digitalmars-d
- Re: memcpy() ... Walter Bright via Digitalmars-d
- Re: memcpy() ... Claude via Digitalmars-d
- Re: memcpy() ... Walter Bright via Digitalmars-d
- Re: memcpy() ... Atila Neves via Digitalmars-d
- Re: memcpy() ... Chris Wright via Digitalmars-d
- Re: memcpy() ... Walter Bright via Digitalmars-d
- Re: memcpy() ... Atila Neves via Digitalmars-d
- Re: memcpy() ... Walter Bright via Digitalmars-d
- Re: memcpy() ... Atila Neves via Digitalmars-d
- Re: memcpy() ... Walter Bright via Digitalmars-d
- Re: memcpy() ... David Nadlinger via Digitalmars-d
- Re: memcpy() comp... Walter Bright via Digitalmars-d
- Re: memcpy() comparison: C, Rust, and D Jack Stouffer via Digitalmars-d
- Re: memcpy() comparison: C, Rust, ... Nick Treleaven via Digitalmars-d
- Re: memcpy() comparison: C, Rust, and D Mathias Lang via Digitalmars-d
- Re: memcpy() comparison: C, Rust, ... Walter Bright via Digitalmars-d
