You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Do you have any thoughts on adding support for the power operator in expressions?
The reason I ask is that looking at the expression documentation, it looks like you're planning to do it.
If you do, could you assign me as the lead for the power operator?
If you do create a power operator, how about a spec like this?
I'm not sure whether pow or power seems appropriate.
pow(path(VirusInRoom::number, 10))
I think it would be appreciated.
P.S.
TMI, but this article was written by the same Korean guy on DeepL with a translator
(he even ran this sentence through the translator)
The text was updated successfully, but these errors were encountered:
I think I forgot to register power as an issue. I'd like you to create it if you don't mind.
The Kotlin JDSL aims to represent the syntax of JPQL directly. This is because I don't want the Kotlin JDSL to become a huddle when creating queries. So it seems like a better way to make it a function named power instead of pow.
I think I forgot to register power as an issue. I'd like you to create it if you don't mind.
The Kotlin JDSL aims to represent the syntax of JPQL directly. This is because I don't want the Kotlin JDSL to become a huddle when creating queries. So it seems like a better way to make it a function named power instead of pow.
Thanks for the quick response hehe
I'll do it with power!
I saw your last commit comment!
You're very diligent :)
Do you have any thoughts on adding
support for the power operator
in expressions?The reason I ask is that looking at the expression documentation, it looks like you're planning to do it.
If you do, could you assign me as the lead for the power operator?
If you do create a power operator, how about a spec like this?
I'm not sure whether
pow
orpower
seems appropriate.I think it would be appreciated.
The text was updated successfully, but these errors were encountered: