Linux

48212 readers

2110 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

434

Rust in Linux lead retires rather than deal with more “nontechnical nonsense” (arstechnica.com)

submitted 2 months ago by tux0r@feddit.org to c/linux@lemmy.ml

213 comments fedilink hide all child comments

Linux people doing Linux things, it seems.

you are viewing a single comment's thread
view the rest of the comments

[–] Giooschi@lemmy.world 5 points 2 months ago (1 children)

For local variables, one should use pointers, otherwise ref does references that are guaranteed to be valid to their lifetime, and thus have said limitations.

Should I take this to mean that pointers instead are not guaranteed to be valid, and thus are not memory safe?

[–] ZILtoid1991@lemmy.world 1 points 2 months ago (1 children)

Pointers are not guaranteed to be safe. DIP1000 was supposed to solve the issue of a pointer referencing to a now expired variable (see example below), but it's being replaced by something else instead.

int* p;
{
  int q = 42;
  p = &q;
}
writeln(*p);     //ERROR: This will cause memory leakage, due to q no longer existing

[–] Giooschi@lemmy.world 3 points 2 months ago (1 children)

Pointers are not guaranteed to be safe

So I guess they are forbidden in @safe mode?

but it's being replaced by something else instead

Do you know what is the replacement? I tried looking up DIP1000 but it only says "superceded" without mentioning by what.

This makes me wonder how ready D is for someone that wants to extensively use @safe though.

[–] ZILtoid1991@lemmy.world 2 points 2 months ago (1 children)

https://github.com/ZILtoid1991/newxml/tree/main

This XML parser of mine uses safe by default.

[–] Giooschi@lemmy.world 2 points 2 months ago

It also seems to require a GC though...

newxml is GC only, for simplicity sake.