List questions from memory-safety | Devhide

Accessing packed field in Rust and Compiler recommendation

Published on 14 March 2024 at 01:11

Safely passing arrays in C

Published on 20 July 2023 at 23:38

What is meant by “An access is instantaneous if it’s not possible for other code to run after that access starts but before it ends” in the Swift Book

Published on 19 March 2023 at 21:25

Does `-fsanitize=bounds-strict` check anything that `-fsanitize=address` does not?

Published on 23 February 2023 at 21:22

Force a std::Vec's capacity to shrink to equal length exactly

Published on 24 November 2022 at 04:54

Rust: can unsafe methods of safe traits be called soundly, even conditionally?

Published on 24 October 2022 at 14:44

Why can't we have a safe ISA?

Published on 15 August 2022 at 02:57

What is an efficient equivalent in C# for Span<Span<T>>, which does not exist?

Published on 27 May 2022 at 13:37

How to judge whether the incoming buffer is valid in C++?

Published on 13 May 2022 at 07:32

Best way to copy bits from a signed to an unsigned variable of same size in C#

Published on 31 January 2022 at 13:50

Arbitrary write vulnerability without buffer overflow

Published on 05 January 2022 at 15:50

why is there a memory confiicting in single thread swift?

Published on 24 December 2020 at 14:19

Is safe recursion possible in C?

Published on 10 November 2020 at 21:08

Does Rust code, statically linked to a C program, gain any beneficial safety properties as a result?

Published on 26 July 2020 at 12:01

Is there a safe alternative to replace the unsafe slice::from_raw_parts for raw pointers?

Published on 01 July 2020 at 18:05

Is Python memory-safe?

Published on 23 May 2020 at 15:23

Why must be structure initialized in rust?

Published on 17 April 2020 at 04:33

How do I set a static lifetime to a returned tuple in Rust?

Published on 04 February 2020 at 04:27

Why does a function have long-term write access to all of its in-out parameters?

Published on 28 January 2019 at 02:55

Are local variables in Swift implicitly initialised to nil when used with UnsafeMutablePointer?

Published on 16 October 2018 at 05:17