Hacker Read
top
|
best
|
new
|
newcomments
|
leaders
|
about
|
bookmarklet
login
uecker
2023-02-20 04:01:13
|
next
[–]
update item
(on:
C-rusted: The advantages of Rust, in C, without the disadvantages
)
Isn't this confusing memory safety with safety?
reply
Loading...
sort by:
oldest
newest
similarity_score
page size:
10
20
50
100
bamboozled | karma 7012 | avg karma 1.83
|
2020-10-12 02:56:41
|
next
[–]
similar comments
(on:
Bit – A modernized Git CLI written in Go
)
Memory safety?
reply
qayxc | karma 3685 | avg karma 2.51
|
2021-06-24 21:10:57
|
next
[–]
similar comments
(on:
NASA can't figure out what's causing computer issues on the Hubble telescope
)
I'm not sure you understand what "memory safety" means.
reply
ctz | karma 2795 | avg karma 5.85
|
2016-12-23 17:16:19+00:00
|
next
[–]
similar comments
(on:
Dramatically Reducing Software Vulnerabilities [pdf]
)
I don't really understand why this doesn't cover memory safety.
reply
hot_gril | karma 4539 | avg karma 1.17
|
2024-06-25 00:14:38
|
next
[–]
similar comments
(on:
More Memory Safety for Let's Encrypt: Deploying ntpd-rs
)
That's not what memory safety refers to.
reply
dbaupp | karma 10204 | avg karma 4.33
|
2019-02-13 16:32:50
|
next
[–]
similar comments
(on:
Rust’s standard library was vulnerable for years and nobody noticed
)
I see no mention of memory safety or unsafety in the issue you linked. Could you be more specific?
reply
jvanderbot | karma 13042 | avg karma 3.94
|
2024-01-03 06:34:42
|
next
[–]
similar comments
(on:
Maestro: A Linux-compatible kernel in Rust
)
This is getting a bit defensive. I think people are interpreting your post as saying all safety is guaranteed by using memory safety, but you rightly walk it back in comments to mean it addresses "primary" security problems.
That's it.
reply
azakai | karma 7684 | avg karma 3.12
|
2021-09-22 15:18:06
|
next
[–]
similar comments
(on:
Swift Regrets
)
Oh right, good point. Other types of memory safety are more relevant here then.
reply
tree_of_item | karma 2524 | avg karma 2.9
|
2017-08-25 13:33:16+00:00
|
next
[–]
similar comments
(on:
Go 1.9 is released
)
This is incorrect. What you're referring to is "memory safety".
reply
nynx | karma 2474 | avg karma 3.75
|
2021-11-15 18:37:55
|
next
[–]
similar comments
(on:
Mako – a full Bitcoin implementation in C
)
its “memory safety”, not “accesses memory”
reply
jobs_throwaway | karma 808 | avg karma 2.49
|
2022-10-18 12:30:15
|
next
[–]
similar comments
(on:
The initial proposal for a C++ Ecosystem International Standard
)
is memory safety not a real problem?
reply
rurban | karma 5612 | avg karma 0.84
|
2022-11-15 23:56:03
|
next
[–]
similar comments
(on:
I enjoy using the Nim programming language at Reddit
)
So memory safety is a cons point now?
reply
Ar-Curunir | karma 3784 | avg karma 2.0
|
2021-07-20 18:13:25
|
next
[–]
similar comments
(on:
A case against security nihilism
)
That's not memory-unsafety. Memory-safety means avoiding bugs like buffer overflow, ROP, etc.
reply
worldsavior | karma 126 | avg karma 0.53
|
2022-12-10 14:10:15
|
next
[–]
similar comments
(on:
Ask HN: When Will Rust-for-Linux Be Completed?
)
Isn't memory safety needed in all cases?
reply
a1369209993 | karma 3438 | avg karma 1.19
|
2020-08-15 18:11:29+00:00
|
next
[–]
similar comments
(on:
Benign data races considered harmful
)
> without any memory safety
Actually, I think that would be memory
protection
, not safety.
reply
cmeacham98 | karma 5725 | avg karma 4.47
|
2024-03-26 21:39:02
|
next
[–]
similar comments
(on:
Rust data structures with circular references
)
The definition of memory safety is not "code that does not result in UB".
reply
AaronFriel | karma 8373 | avg karma 7.29
|
2022-08-24 01:03:31
|
next
[–]
similar comments
(on:
Oven: The Company Behind Bun
)
I misspoke, there is a gradient in safety, but "memory safe" is binary.
reply
extrememota | karma | avg karma
|
2021-01-27 16:48:46
|
next
[–]
similar comments
(on:
Confession Of A C/C++ Programmer (2017)
)
Memory safety is not the only type of safety though. There are race conditions for example.
reply
pohl | karma 9288 | avg karma 3.55
|
2023-03-04 10:29:43
|
next
[–]
similar comments
(on:
Oxidizing bmap-tools: rewriting a Python project in Rust
)
Interesting, I hadn’t realized how much the phrase “memory safety” understates what is desirable.
reply
noelwelsh | karma 8125 | avg karma 4.48
|
2023-12-20 09:04:47
|
next
[–]
similar comments
(on:
MiniLang: A type-safe C successor that compiles directly to x86_64 assembly
)
Memory safety and type safety are different things. They usually go together, but not necessarily so.
reply
next
Legal
|
privacy
reply