Re:C-for-all: Extending C with modern safety and productivit...
by GlitchMr on Wednesday December 04, 2019 @06:15AM
(#21701253)
The function that calls `new_point`, the value is moved. Similarly, consider the following case.
Assuming `struct Point` has a destructor, this would move `a` into `a2`, and prevent accesses to `a` after `a2` assignment, as `a` is no longer considered to be alive at this point. C++ has a wrong default of cloning instead of moving, but a new language could fix that.
[ Parent
| on HN ]
Re:C-for-all: Extending C with modern safety and productivit...
by wwright on Wednesday December 04, 2019 @06:59AM
(#21701439)
That default changes in C++11: https://en.cppreference.com/w/cpp/language/copy_elision
The logic around it is still pretty complicated, since we’re talking about C++.
Re:C-for-all: Extending C with modern safety and productivit...
by zabzonk on Wednesday December 04, 2019 @06:47AM
(#21701374)
> C++ has a wrong default of cloning instead of moving
Which it inherited from C.
Re:C-for-all: Extending C with modern safety and productivit...
by madmax96 on Wednesday December 04, 2019 @06:38AM
(#21701339)
Why is cloning rather than moving the wrong default?
Re:C-for-all: Extending C with modern safety and productivit...
by gmueckl on Wednesday December 04, 2019 @06:59AM
(#21701442)
It isn't. Cloning is what actually happens under the hood, if a and a2 are in different memory locations. Making a inaccessible after the assignment is merely a convention. With a struct that only has data members, there are no further consequences.
If the struct contains a pointer, you need a kind of additional contract that says how the memory that is pointed to is going to be managed, particularly when it is going to be freed and by whom. And that is where move semantics establish a constricting convention that is intended to make that unambiguous.
Re:C-for-all: Extending C with modern safety and productivit...
by saagarjha on Wednesday December 04, 2019 @06:37AM
(#21701337)
So you’re looking for Rust with C’s syntax?
Re:C-for-all: Extending C with modern safety and productivit...
by F-0X on Wednesday December 04, 2019 @06:51AM
(#21701390)
Would be a big improvement on Rust.
Re:C-for-all: Extending C with modern safety and productivit...
by wwright on Wednesday December 04, 2019 @07:01AM
(#21701452)
What part of Rust’s syntax do you think is a detriment vs C? A lot of it is very similar to C, but with ambiguity removed.
- Variable types are changed to avoid ambiguity in lexing.
- Loops and conditionals require {}, which means the parentheses can be dropped on the condition and there’s no ambiguity about nested if’s and else’s.
What would you like improved?