Conversation

Notices

1. Disinformation Purveyor :verified_think: (thatguyoverthere@shitposter.club)'s status on Thursday, 30-Mar-2023 21:18:57 JST Disinformation Purveyor :verified_think:

   • verified neko :verified::verified::verified::makemeneko:
   • Paulo
   • brea
   • Abby!!!
   • Node
   @paulo @roboneko @Abby @node @driftwood the problem is that parseInt says an empty string is not a number (agreed) but isNaN does not.
   • Disinformation Purveyor :verified_think: (thatguyoverthere@shitposter.club)'s status on Thursday, 30-Mar-2023 21:23:13 JST Disinformation Purveyor :verified_think:

     in reply to

     • verified neko :verified::verified::verified::makemeneko:
     • Paulo
     • brea
     • Abby!!!
     • Node
     @paulo @Abby @driftwood @node @roboneko here's another one.
     
     Let's say you have a string '100021_00'. parseInt will not stop and say 'woah not a number' like it did with the empty string. Instead it will return the 100021 portion. This means that the previous test of using `isNaN(parseInt('100021_00'))` will return false. if you check isNaN on the string itself it will say it's not a number.
   • Disinformation Purveyor :verified_think: (thatguyoverthere@shitposter.club)'s status on Thursday, 30-Mar-2023 21:47:34 JST Disinformation Purveyor :verified_think:

     in reply to

     • verified neko :verified::verified::verified::makemeneko:
     • Paulo
     • brea
     • Abby!!!
     • Node
     @roboneko @Abby @paulo @node @driftwood yeah parsing it as int and returning the integer bits would make more sense than truncating it I agree :shrug:
   • verified neko :verified::verified::verified::makemeneko: (roboneko@bae.st)'s status on Thursday, 30-Mar-2023 21:47:35 JST verified neko :verified::verified::verified::makemeneko:

     in reply to

     • Paulo
     • brea
     • Abby!!!
     • Node
     @node @thatguyoverthere @Abby @paulo @node @driftwood that's terrible. error, understandable. xxx_yy return xxxyy would be perfectly reasonable (common string literal notation). xxx_yy -> xxx is simply wrong
     Disinformation Purveyor :verified_think: likes this.
   • Disinformation Purveyor :verified_think: (thatguyoverthere@shitposter.club)'s status on Thursday, 30-Mar-2023 21:56:19 JST Disinformation Purveyor :verified_think:

     in reply to

     • verified neko :verified::verified::verified::makemeneko:
     • Paulo
     • brea
     • Abby!!!
     • Node
     @roboneko @Abby @driftwood @node @paulo
     
     ```
     parseInt('s100') // NaN
     parseInt('100s') // 100
     ```
   • Disinformation Purveyor :verified_think: (thatguyoverthere@shitposter.club)'s status on Thursday, 30-Mar-2023 22:25:25 JST Disinformation Purveyor :verified_think:

     in reply to

     • verified neko :verified::verified::verified::makemeneko:
     • Paulo
     • brea
     • Abby!!!
     • Node
     @roboneko @Abby @paulo @node @driftwood you can see from above it's not just _ but any string that starts with digits seems to parse into *something*
   • verified neko :verified::verified::verified::makemeneko: (roboneko@bae.st)'s status on Thursday, 30-Mar-2023 22:25:26 JST verified neko :verified::verified::verified::makemeneko:

     in reply to

     • Paulo
     • brea
     • Abby!!!
     • Node
     @node @thatguyoverthere @Abby @paulo @node @driftwood _ is a special case because string literal notation. same for ' but you probably don't want 123xyz456abc000 to successfully parse that seems obviously wrong
     
     also I don't think 1___2 should parse either, just that 1_2 is reasonable enough to interpret as 12
     Disinformation Purveyor :verified_think: likes this.