"I mean, which pointer should I use? How should I iterate? I'm sure there's an answer to this, but I just found it easier to go back to python and hit up rust when I needed it."
You can of course use Python. But we are talking about languages with different applications. You want fast development hand have no expectations on speed? Use Python! You want to control your computer to get maximum performance with a safe type system? Use C++!
Since you are already talking about pointers: In Python you are not even given the chance to do all the stuff you can do in C++. You have to rely on garbage collection (and "del"). That is an entirely different thing than C++ where you exactly control how long your objects should live.
For the pointers (order I would suggest):
1) No pointers, use references whenever possible
2) Use std::unique_ptr
3) Use std::shared_ptr
You can also try to use shared_ptr all the time if it makes your transition from Python more easy. It is not optimal, but it may get you started.
And do not start wrapping your head around rvalue references right from the beginning. This is a very special topic, which you can ignore as a beginner.
I have the same problem with FreeCAD: I really want to uae FreeCAD. But after some weeks or months I cannot even remember simple things like how to add a new object (or hole) to a face of an object.
Yes, a lot of the ideas are not new.
Nevertheless, it is currently an active field of research. One of them is "Integrated Sensing and Communication" (ISAC [or ICAS/JC&S/...]).
One idea is to exploit the signal's structure - despite simply trying to correlate the received line-of-sight signal with its delayed copies.
Especially OFDM has a nice structure. You can estimate delays (-> distances) as frequencies along the subcarriers and Doppler shifts (-> velocities) as frequencies along consecutive OFDM symbols. Estimators like maximum likelihood, ESPRIT, MUSIC, and compressed sensing etc. are your friends here for high-resolution results.
Unfortunately OFDM has a problem with large Doppler shifts (velocities). Therefore, people are looking at other multiplexing schemes like OTFS or AFDM.
I am not sure about other EU countries, but in Germany you have the right to lie in this situation since the question was very likely illegal in the first place. There are other topics which an employer is not allowed to ask about in German. For example about pregnancy or planned pregnancy. You always have the right to lie when you get one of these questions.
They're representative of scenarios which your application can enter.
So if the tests were mocked and a bug went live he'd still notice, after all it means your software behaved incorrectly and now you gotta clean up the pieces.
This is becoming cyclical, did you forget what this comment chain went about?
The discussion went from tests being written by ai, to nobody actually reviewing the tests, to the claim that given those circumstances, you wouldn't notice that the tests may not tests anything anymore because of mocks.
My statement was merely pointing out that your previous comment was groundless because they still would've found out about those bugs when they went live.
>My statement was merely pointing out that your previous comment was groundless because they still would've found out about those bugs when they went live.
That's a big issue in my team. We cannot really review tests manually, we already have too much just reviewing the code. And even then, sometimes the 'is this change necessary' question is forgotten or ignored (happened to me 20 minutes ago) because I an tired of fighting my junior+AI. I try to make AI refactor the tests every weeks ande that's it.
> Are people reviewing all the tests that have been created automatically?
Absolutely not! Some people ask a code assistant to write only integration/end-to-end tests and commit them. Unittests is only to help LLM generate correct code.
You can of course use Python. But we are talking about languages with different applications. You want fast development hand have no expectations on speed? Use Python! You want to control your computer to get maximum performance with a safe type system? Use C++!
Since you are already talking about pointers: In Python you are not even given the chance to do all the stuff you can do in C++. You have to rely on garbage collection (and "del"). That is an entirely different thing than C++ where you exactly control how long your objects should live.
For the pointers (order I would suggest): 1) No pointers, use references whenever possible 2) Use std::unique_ptr 3) Use std::shared_ptr
You can also try to use shared_ptr all the time if it makes your transition from Python more easy. It is not optimal, but it may get you started.
And do not start wrapping your head around rvalue references right from the beginning. This is a very special topic, which you can ignore as a beginner.
reply