Have to add that we work exclusively in strongly-typed languages. Kinda want to see how it plays out, but I can’t help but argue with him, so I think I’ll just go.
What is this a screenshot of?
Deep Rock Galactic, an awesome pve/coop game :)
The game “Deep Rock Galactic”
Space dwarves (solo or co-op) mining in procedurally generated caves while getting bugged by the local fauna.
There are a few different mission types, four unique classes and a vast weapon upgrade system to explore.
Also features the best (non-voip) communication system ever.
Highly recommend. Rock and Stone!
mushrum
Rock and roll and stone!
So, using
void *for everything?I worked as a subcontractor with a lead architect that used casting to void * as an only method of sending data. Argument to a function? Void *. Return value? Void *. Multithread pipe? Cast to a void *, no big deal. 80% of my job was investigating segfaults. 20% was heavy drinking to prevent suicidal thoughts.
I do mainly C and C++ and for a while, I had to check out some JS code…
I wouldn’t want to take your place.The only case I remember using a
void*in is when passing a function as an argument for a callback, to an RTC peripheral. Even then, the function was returning avoid.
Strong-type for Karl!
Did you know that the type of a variable is determined by the frequency of plasma oscillations among the objects valence electrons?
I recently tried out Python. I had no idea it still doesn’t have runtime enforced typing…
I didn’t realize that PHP was decades ahead of it.
Python is dynamically strong typed, meaning you don’t need to specify any types, but unlike JavaScript you can’t just use a string where an int was expected. In that sense it’s absolutely runtime enforced typing.
… and yet… it lacks clear and enforced type restrictions which help with clear code contracts. It’s certainly better than Javascript but the lack of runtime enforced type checking can force defensive programming in an unnecessary manner.
Your statement isn’t strict type checking. It’s a restricted form of type coercion. Given how common this feature is in other languages it’s weird that pythonistas feel so defensive when discussing the feature. I enjoy strict type checking, but that’s my opinion - it makes it a poor choice for the sorts of projects I work on but if it’s good for you then enjoy!
You said it’s not runtime type checking but then switched to “strict type checking” - those aren’t the same. Other person has it right, it has runtime type checking. The type checking happens when running your code. I don’t think that’s particularly useful, it’s pretty much sugar on top of what would throw an error anyway.
it lacks clear and enforced type restrictions which help with clear code contracts
Not anymore! Gradual typing is supported by the core language and pyright is a fantastic incremental type checker that you can use both in your editor and in CI.
Python 3.x will never have static typing because that would break backwards compatibility.
However, typing hints have been Integrated into Python for a while, and you are heavily recommended to use them, so your IDE can enforce typing.
Considering there is typing in the code why is there no switch to enable type checking at runtime? PHP does this with a per file
declare(strict_types)- why would python be unable to have either a global or per file flag to enable checks?Typing when you need it gives you more freedom over a toggle. You can choose to type some parts of the code while leaving other parts untyped.
For example, if I’m writing a quick and simple Python script I may forgo typing, but when iterating on it I’d go back and add the types I need.
This isn’t an issue, though. PHP has the same partial typing flexibility. There are ways to solve that issue and even typed PHP still allows union types including
mixedwhich allows any types.
why is there no switch to enable type checking at runtime?
Have you got problems this would solve? I’ve done a lot of type annotated Python at scale and I can’t think of an example.
Edit: given nobody in their right mind allows code that’s not checker clean.
Also have the option of selectively/strictly enforcing in CI, to get an experience & protections similar to “compile-time type checking”
i mean yeah it’s a scripting language, what did you expect?
do you want bash to add typing as well?
apparently it’s a feature
apparently it’s a feature
What about the caller? IMO types are more helpful for the consumer of the code than the original developer.
You don’t have to worry about that if nobody uses your code. taps temple
That guy in corporate is creepy as fuck. I think he’s a pedophile. He’s always saying “TIME TO GET BUSY MINORS!”
Did I hear a Rock and Stone?
