You're not performing any kind of magic or conversion when performing casting, you're essentially telling the compiler trust me, i know what i'm doing and i can guarantee you that this. In absence of op's clarification, this question could be interpreted in the sense of converting any string to a number, i.e Is there a possibility that casting a double created via math.round() will still result in a truncated down number no, round() will always round your double to the correct value, and then, it will be cast to an long which will truncate any decimal places.
Episode 1: The Casting Couch with Brooke Ashton (Emily Kosloski
Direct casting types don't have to be strictly related
It comes in all types of flavors
Usually a new object is created Copy and information might be lost Change reference type, otherwise throws exception. Had you been doing just double x = a;, you can do away with the explicit conversion since an int is implicitly converted to a double (live example).
Static cast is also used to cast pointers to related types, for example casting void* to the appropriate type 'casting' with reflection asked 16 years, 1 month ago modified 4 years, 6 months ago viewed 65k times Do you understand the concept of casting Casting is the process of type conversion, which is in java very common because its a statically typed language
Casting has sense only for a variable (= chunk of memory whose content can change) there are no variables whose content can change, in python
There are only objects, that aren't contained in something They have per se existence Then, the type of an object can't change, afaik Then, casting has no sense in python
That's my believing and opinion Correct me if i am wrong, please
