somewhat annoying, in my opinion

i suspect for the masses bitwise operations aren't all that common

i would have preferred named functions for boolean operators and symbols for bitwise

there's probably (hopefully?) other factors that went into the decision that i'm not aware of

Damn

Annoying to have to do

foo = foo or it

Ah well

@redrield If it's any consolation, Swift recently removed

++

and replaced it with

+=

Yeah

I'm aware of that

i tend to support that change

python users don't seem to miss it

++

tends to only be used "cleverly" these days, to the detriment of readability

It's pretty universally readable. Sequence points and whether it returns a value were some of the factors behind Swift's decision

good for them

do they have sane bitwise operators too?

i might be a convert

they have user-defined operators

As much as I like bit twiddling, I can't imagine that a language's take on bit arithmetics would ever be a factor in me picking that language

well it's pretty awful in Kotlin

i would never choose the language for dealing in bits

if you're at that level best to stay in Java

One would say C

and millions wouldn't

we can leave that one person alone to their vices

If you're bit twiddling, that code probably isn't getting much use of Kotlin's features anyway

eh, i dunno. inline functions let you wrap high-level abstractions around low-level primitives like bits

without overhead, being the important factor

true

i suppose it all depends!