You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Page: Why dynamic types are even worse for someone with an visual impairment
Paragraph: What's the difference?
Text in question:
Here is an example so you can see how the types behavior differently in different languages.
Here is an example in python. Python has a dynamic type system.
# x is a string here
x ="this is a string"
x is a a integer here
x = 42
Note that the types change here, this is different from shadowing in rust
So as we see, a was first an integer and now it's a string. This compiles as expected because python has dynamic types.
The issue is that the variable a is not in the code. a should be x. Also, it says that the variable was first an integer and then a string. But in reality it first was a string and then an integer.
The text was updated successfully, but these errors were encountered:
Page: Why dynamic types are even worse for someone with an visual impairment
Paragraph: What's the difference?
Text in question:
Here is an example so you can see how the types behavior differently in different languages.
Here is an example in python. Python has a dynamic type system.
x is a a integer here
x = 42
Note that the types change here, this is different from shadowing in rust
So as we see,
a
was first an integer and now it's a string. This compiles as expected because python has dynamic types.The issue is that the variable
a
is not in the code.a
should bex
. Also, it says that the variable was first an integer and then a string. But in reality it first was a string and then an integer.The text was updated successfully, but these errors were encountered: