Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong order types #60

Open
Aangepast opened this issue Sep 17, 2024 · 0 comments
Open

Wrong order types #60

Aangepast opened this issue Sep 17, 2024 · 0 comments

Comments

@Aangepast
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant