That's silly. Luckily, I don't think this was the same situation. This was at a university and they had classes with other languages. The beginner classes were split into two variants, where some students (mostly CS students) learned C, and other students (economy, etc.) learned Python. I suppose they figured it was more useful to them or something.
Ogeon
I was a teacher's assistant in beginner's programming at university for a bit. I expected them to learn C, which I knew enough of, but I got assigned to a group that learned Python instead. I had never used Python at the time. I ended up having to speed learn it while trying to teach it, to not be completely useless.
That's definitely part of "the deal" with MIT and Apache. The other end of it is that they shouldn't really expect to get anything more than what the authors are willing to give.
Zooming in? In this economy?!
"Search prompt engineer"
Simple features are often complex to make, and complex features are often way too simple to make.
It's useful for keeping track of your mental gymnastics.
I don't know, something about seeing the same diarrhea pills ad over and over doesn't exactly spark joy for me.
It may be possible to use the Any
trait to "launder" the value by first casting it to &Any
and then downcasting it to the generic type.
let any_value = match tmp_value {
serde_json::Value::Number(x) => x as &Any,
// ...
};
let maybe_value = any_value.downcast_ref::< T >();
I haven't tested it, so I may have missed something.
Edit: to be clear, this will not actually let you return multiple types, but let the caller decide which type to expect. I assumed this was your goal.
My shower has its own favorite temperature and will slowly readjust itself to it.
Reject C, return to assembly. Structured programming is the true oppression our generation never talks about.