Is it a known bug that this terminates at `UInt.MAX_VALUE` instead of `UByte.MAX_VALUE`? ``` fun mai...

# announcements

[Ruckus]

Is it a known bug that this terminates at UInt.MAX_VALUE instead of UByte.MAX_VALUE?

fun main() {
    for (x in UByte.MIN_VALUE..UByte.MAX_VALUE) {
        println(x)
    }
}

[streetsofboston]

It works for me…. it prints out the value 0 through `255`….

[Ruckus]

Really? keeps right on going and printing values up to UInt.MAX_VALUE for me.

[Ruckus]

Running it in https://pl.kotl.in/H_6davVCu has some really weird behavior. It runs the previously entered program, and doesn't actually run this one...

[streetsofboston]

I ran it using Android Studio, not on the kotlin playground

[Ruckus]

I tried it both in IntelliJ and in the playground. In intelliJ it goes up to UInt.MAX_VALUE, and the playground does what I mentioned above (try clicking it and see if you get the same as I)

[Ruckus]

I decided to file a bug. We'll see if anyone else can reproduce it: https://youtrack.jetbrains.com/issue/KT-32044?project=kt

[streetsofboston]

How long does it take until it gets to UInt.MAX_VALUE?

[streetsofboston]

It works on Android Studio; I tried Kotlin version 1.2.1 and 1.3.0-M1

[Ruckus]

A long time. You can shorten it by removing the `println`:

fun main() {
    var n = 0u
    for (x in UByte.MIN_VALUE..UByte.MAX_VALUE) {
        n = x
    }
    println(n)
}

That returns quickly and prints UInt.MAX_VALUE

[LS]

I tried it in IntelliJ and got the same (unexpected) result, but the IDE screams about unsigned types being experimental, so I guess bugs are to be expected

[streetsofboston]

Weird that running it in Android Studio works fine….

[Ruckus]

@streetsofboston Could you add that to the issue? That's good information to have.

[streetsofboston]

Done 🙂

[streetsofboston]

Also, I run it on a Mac

[Ruckus]

Sweet, thanks

[Ruckus]

I guess I should add what I'm running on to the issue., but I'm on Windows 10 using IntelliJ 2019.1.3 and Kotlin 1.3.31

[Ruckus]

Hmm, changing the playground to use JS appears to fix the issue too...

[streetsofboston]

When you replace UByte.MIN_VALUE and UByte.MAX_VALUE with 0 and 255, it works fine

[Ruckus]

Indeed, it has to be when you use the constants for some reason. I'm not sure if it has something to do with the constants themselves, or with the fact that x gets converted to UInt.

[streetsofboston]

How do you get Kotlin 1.3.31… it doesn’t exist on my end…

[Ruckus]

It was released in April (on the 25th), so IDEA just updated automatically a while ago

[streetsofboston]

NVM… i was talking about Coroutines version…. 😕
🙂

[Ruckus]

Ah 🙂

[streetsofboston]

going to Kotlin 1.3.31 also shows the problem on my end

[Ruckus]

Interesting, looks like it was a regression somewhere then.