Remote
0
Followers
0
Following
14
Posts
Joined November 06, 2022
Posts
Open post
Replying to
@filippo@abyssdomain.expert
@filippo@abyssdomain.expert wait let me understand.
he claim that if he change a line of code, and don't run the project's test, then you have critical bugs?
0
0
0
0
Open post
Replying to
@mikarv@someone.elses.computer
@mikarv@someone.elses.computer pre-AI, 99.999% of my project sit on the shelf.
No ral change there.
are those wasted time?
no, that is how I learn ambedded, code architecture, how I explored from android app to making schematics to webapp.
Now is just about learning new tool; such level of weapknized autism on a production codebase, if property managed, is a godsent.
0
0
0
0
Open post
Replying to
@gregkh@social.kernel.org
@gregkh stupid question that is not asked enough:
do you think that the way rust can describe and enforce state machines and complex states/types, would generally force to build better architecture?
Or, the lack of (in)adaptability of the system will be more problematic in the long run?
0
1
0
0
Open post
Replying to
@Mara@hachyderm.io
@Mara@hachyderm.io nope, but they started leaking password too now: https://www.reddit.com/r/cpp/comments/1nswi4s/til_that_the_wg21_wiki_is_still_running_off_a/
0
0
0
0
Open post
Replying to
@lesto@hachyderm.io
@asperamanca@mastodon.social
@PeterSommerlad@mastodon.social @DanielaKEngert@hachyderm.io @alilleybrinker@hachyderm.io
I don't know why, but on baremetal, pretty much any legacy project I worked on failed to a correctly use atomic/mutex, maybe because early version of C and C++ did not had them in STD.
Rust still have issue in that too; will happily let you call blocking function in interrupt (deadlock).
But we are excluding so much potential per error, errors I see in production code already..its a huge step for baremetal embedded.
0
0
0
0
Open post
Replying to
@asperamanca@mastodon.social
@asperamanca@mastodon.social
@PeterSommerlad@mastodon.social @DanielaKEngert@hachyderm.io @alilleybrinker@hachyderm.io not only that. Take a look at embassy-rs for embedded. At compile time, it make sure your resources (DMA, GPIO, Peripheral, Timer) are correctly assigned, never double assigned unless you deinit whatever had them in use.
This is all based on the borrow system and can't be express in C++.
Rust itself make sure you use Atomic or Mutex value to share variable between functions (interrupt handler to tasks/main thread), a common error
0
1
0
0
Open post
Replying to
@lesto@hachyderm.io
@PeterSommerlad@mastodon.social @DanielaKEngert@hachyderm.io @alilleybrinker@hachyderm.io Still about MISRA, that is pretty much kinda what expect "profiles" for C++ may be: a good idea, but really the lack of language/limitation of the legacy, make it a "good enough but surely could be better".
1
0
0
0
Open post
Replying to
@PeterSommerlad@mastodon.social
@PeterSommerlad@mastodon.social @DanielaKEngert@hachyderm.io @alilleybrinker@hachyderm.io > strengthen my take that education is lacking
wouldnt be great if the compiler/tools would be the one doing the education, not letting you do "bad" stuff unless explicitly?
Ongoing work
How does this help me to not do those error?
MISRA-C++ guidelines
All C++ programmer should follow MISRA-C++? Because otherwise is not really comparable to other lang with those safety by default. BTW i am not aware of any free tool that enforce the rules.
0
1
0
0
Open post
Replying to
@lesto@hachyderm.io
@DanielaKEngert@hachyderm.io @PeterSommerlad@mastodon.social @alilleybrinker@hachyderm.io I really don't understand how someone can say "C++ is safe, just follow those rules", and those rules are a vague concept, that vary over time and whoever you ask, and with no real enforcement assisted by tooling.
There is POTENTIAL from C++, but lack of teaching (from schools), lack of tooling, and lack of good guidelines (Core Guidelines are great, but you need to know what you are looking for) signal it is not as ready as other lang are.
1
1
0
0
Open post
Replying to
@DanielaKEngert@hachyderm.io
@DanielaKEngert@hachyderm.io @PeterSommerlad@mastodon.social @alilleybrinker@hachyderm.io well, they may be easy to grasp if you know what are, but that is the issue. You come up with your specific (or better, non-specific) set of rules.
How am i supposed to know about them, learn and teach them, if there is no agreement?
Core Guidelines is all we have and is an amazing step forward.
Too bad there is no tooling to enforce.
Peter: compiler warning never told to prefer a smart pointer where i used raw, or get(i) instead of [i]
1
1
0
0
Open post
Replying to
@DanielaKEngert@hachyderm.io
@DanielaKEngert@hachyderm.io @PeterSommerlad@mastodon.social @alilleybrinker@hachyderm.io i just searched "contemporary C++" and i cant find a single clear definition. Some talk, some say it is Modern C++ that itself is not super clear (I assume it means follow the Core Guidelines).
What a mess of a definition for noobs like me!
There is no way to programmatically enforce those guidelines (profiles?), so those issue are not "ruled out".
Im bad at remembering stuff and follow the new std.
I want the language to work with and for me
1
1
0
0
Open post
Replying to
@chrisisgr8@tech.lgbt
@chrisisgr8 oh come on, dont be like this, they still have 6 more full years to best themself. This is just the tip, if it hurt already, get ready for the shaft
0
0
1
0
Open post
Replying to
@GreenFire@mstdn.social
@GreenFire@mstdn.social @michaelgemar@mstdn.ca @theogrin@chaosfem.tw @maxkennerly@mstdn.social but so far they did, falcon 9 is the cheapest access to space in terms of $/kg
0
0
0
0
Remote instance
hachyderm.io
Open on original server