And that's how I ended up on mastodon
-
@elyn Yeah, I advise folks to steer clear of the core type machinery implementation unless they actually *want* to stretch their brains into weird shapes in order to understand it. Lots of "this isn't quite true yet, but it will be true before it needs to be true, just trust us on that, computer".
I also love the fact that it is all completely *un*necessary knowledge for folks that just want to use Python without worrying about the fiddly details of how it works.
@ancoghlan I love fiddly details and non-euclidean neurology! It's good compilers don't appear to be conscious. I can't fathom the depths of their paranoia if they had to experience all the lies and coercion we put them through
-
And that's how I ended up on mastodon
That's a hit toot on Mastodon
I got it from the trending bot so, yeah, that's indeed a hit toot on Mastodon -
And that's how I ended up on mastodon
@elyn Some days I wake up and decide I want to invent a new type of number. I'm glad Python supports this.
-
And that's how I ended up on mastodon
@elyn you found The Place (tm)
-
And that's how I ended up on mastodon
@elyn omg I was right holy shit
-
@elyn omg I was right holy shit
@ArchiteuthisFlux YOU REALLY WERE, OMG
-
That's a hit toot on Mastodon
I got it from the trending bot so, yeah, that's indeed a hit toot on Mastodon@csolisr @ArchiteuthisFlux is a prophet, truly
-
@ancoghlan I love fiddly details and non-euclidean neurology! It's good compilers don't appear to be conscious. I can't fathom the depths of their paranoia if they had to experience all the lies and coercion we put them through
@elyn @ancoghlan a lot of the python internal type machinery was added before python had spellable types, which now shows up as those strange breaks in the type math.
there's a similar case where `float` actually means `float | int`, so there's now no way of saying just float, no int, even though `isinstance(1, float) == False`.
-
@csolisr @ArchiteuthisFlux is a prophet, truly
-
@elyn @ancoghlan a lot of the python internal type machinery was added before python had spellable types, which now shows up as those strange breaks in the type math.
there's a similar case where `float` actually means `float | int`, so there's now no way of saying just float, no int, even though `isinstance(1, float) == False`.
@konstin @ancoghlan Maybe they should just change it, surely there's no historical precedent indicating that changing foundational design details would ever stifle adoption or fracture a community!
-
@elyn @ancoghlan a lot of the python internal type machinery was added before python had spellable types, which now shows up as those strange breaks in the type math.
there's a similar case where `float` actually means `float | int`, so there's now no way of saying just float, no int, even though `isinstance(1, float) == False`.
@konstin @ancoghlan That's genuinely really cool to know tho, thank u
-
And that's how I ended up on mastodon
@elyn I was about to ask you for a link to the original Mastodon post, to be able to boost that one and to give the author credit. Luckily I read the last post just before posting myself :D.
Edit: And hi and welcome
-
@elyn I was about to ask you for a link to the original Mastodon post, to be able to boost that one and to give the author credit. Luckily I read the last post just before posting myself :D.
Edit: And hi and welcome@T_X thank you!! And hey, if you're looking for anyone else to give some credit to, check out @ArchiteuthisFlux , the post wouldn't exist without him telling me it'd be well received here!
-
And that's how I ended up on mastodon
@elyn Welcome!
-
@elyn @ancoghlan a lot of the python internal type machinery was added before python had spellable types, which now shows up as those strange breaks in the type math.
there's a similar case where `float` actually means `float | int`, so there's now no way of saying just float, no int, even though `isinstance(1, float) == False`.
@konstin @elyn Oof, I had managed to forget how much worse it all was before the classic class emulation bits were dropped, but that observation reminded me. I shudder to think how much harder it would have been to start defining type forms if those were still around (as you say, it's hard enough retrofitting a comprehensive description language to the status quo).
-
@elyn Yeah, I advise folks to steer clear of the core type machinery implementation unless they actually *want* to stretch their brains into weird shapes in order to understand it. Lots of "this isn't quite true yet, but it will be true before it needs to be true, just trust us on that, computer".
I also love the fact that it is all completely *un*necessary knowledge for folks that just want to use Python without worrying about the fiddly details of how it works.
@ancoghlan @elyn I didn't mean to, but I have been in the past couple days, and I am not even working in anything conceptually complex
-
And that's how I ended up on mastodon
@elyn Welcome!
I'd say I hope you'll like it here, but I have a feeling that you will!
-
@elyn Welcome!
I'd say I hope you'll like it here, but I have a feeling that you will!
@stefan and you're so right!
-
@ArchiteuthisFlux @csolisr the alchemical formula for mastodon catnip has thus been revealed
