sure would be nice to have `^` as a power operator

# getting-started

[Hullaballoonatic]

sure would be nice to have ^ as a power operator

[Sam]

keep in mind, ^ is xor in C and having that as power could be misleading

[elizarov]

➕ For C-family of languages, ** as a power looks better.

[Hullaballoonatic]

fair enough, so why wouldn't kotlin include **?

[Hullaballoonatic]

i know i can make an infix ``**`` but i dun wanna ;_;

[elizarov]

https://youtrack.jetbrains.com/issue/KT-26814

[Hullaballoonatic]

they might as well get on introducing ^ for "or" functions too. I know they currently have and, or, xor etc boolean operators, but it seems like a waste to not make use of these free characters :S

[Hullaballoonatic]

like it's strange they don't use & and ^ for boolean and and or when they already use ! for boolean not

[Hullaballoonatic]

or they could also use && and || for bitwise operators too 🤷‍♂️

[elizarov]

https://youtrack.jetbrains.com/issue/KT-1440

[Hullaballoonatic]

7 years old 😮

[Hullaballoonatic]

but hey kt-1440

[Hullaballoonatic]

"The main reason why the features you implemented are not in the language yet is that there are many questions about possible better uses of the syntactic elements they employ. There are very few special characters on our keyboards, so we have to be very cautious here. My personal hunch is that | and & have a decent chance of becoming overloadable operators in Kotlin at some point, but it’s less likely for ^, <<, >>, >>>. In any case, to make such decisions we have to finalize a few other bigger features with high syntactic uncertainty: collection literals, some DSL-related features, etc."

[Sam]

There was a survey for collection literals

https://blog.jetbrains.com/kotlin/2017/06/kotlin-future-features-survey-results/

[Sam]

And a workaround for the same

https://twitter.com/marcinmoskala/status/1007640373970329600/photo/1?ref_src=twsrc%5Etfw%7Ctwcamp%5Etweetembed%7Ctwterm%5E1007640373970329600%7Ctwgr%5E373939313b636f6e74726f6c&amp;ref_url=https%3A%2F%2Fblog.kotlin-academy.com%2Fmedia%2F056ef2cb1887537e4a1f7f9acf0f9d13%3FpostId%3Da225dbb004a6

[Hullaballoonatic]

thanks for sharing

[Hullaballoonatic]

reading through the proposed features, i could not want collection literals and collection comprensions harder

[Hullaballoonatic]

oh fuck, and inline classes for units of measurement, though i do really enjoy https://git.tenkiv.org/software/Physikal

[Hullaballoonatic]

i also really support "no comma after any element of a list if it's followed by a new line"

[Hullaballoonatic]

that would be great for constructors

[Hullaballoonatic]

although a lot of these features feel like.... why is this even a question? (e.g. unsigned types, SAM conversions)

[Hullaballoonatic]

nvm, though, 1.3 is bringing quite a few of them, including inline classes, and unsigned ints 😄