https://kotlinlang.org logo
Channels
100daysofcode
100daysofkotlin
100daysofkotlin-2021
advent-of-code
aem
ai
alexa
algeria
algolialibraries
amsterdam
android
android-architecture
android-databinding
android-studio
androidgithubprojects
androidthings
androidx
androidx-xprocessing
anime
anko
announcements
apollo-kotlin
appintro
arabic
argentina
arkenv
arksemdevteam
armenia
arrow
arrow-contributors
arrow-meta
ass
atlanta
atm17
atrium
austin
australia
austria
awesome-kotlin
ballast
bangladesh
barcelona
bayarea
bazel
beepiz-libraries
belgium
benchmarks
berlin
big-data
books
boston
brazil
brikk
budapest
build
build-tools
bulgaria
bydgoszcz
cambodia
canada
carrat
carrat-dev
carrat-feed
chicago
chile
china
chucker
cincinnati-user-group
cli
clikt
cloudfoundry
cn
cobalt
code-coverage
codeforces
codemash-precompiler
codereview
codingame
codingconventions
coimbatore
collaborations
colombia
colorado
communities
competitive-programming
competitivecoding
compiler
compose
compose-android
compose-desktop
compose-hiring
compose-ios
compose-mp
compose-ui-showcase
compose-wear
compose-web
confetti
connect-audit-events
corda
cork
coroutines
couchbase
coursera
croatia
cryptography
cscenter-course-2016
cucumber-bdd
cyprus
czech
dagger
data2viz
databinding
datascience
dckotlin
debugging
decompose
decouple
denmark
deprecated
detekt
detekt-hint
dev-core
dfw
docs-revamped
dokka
domain-driven-design
doodle
dsl
dublin
dutch
eap
eclipse
ecuador
edinburgh
education
effective-kotlin
effectivekotlin
emacs
embedded-kotlin
estatik
event21-community-content
events
exposed
failgood
fb-internal-demo
feed
firebase
flow
fluid-libraries
forkhandles
forum
fosdem
fp-in-kotlin
framework-elide
freenode
french
fritz2
fuchsia
functional
funktionale
gamedev
ge-kotlin
general-advice
georgia
geospatial
german-lang
getting-started
github-workflows-kt
glance
godot-kotlin
google-io
gradle
graphic
graphkool
graphql
graphql-kotlin
graviton-browser
greece
grpc
gsoc
gui
hackathons
hacktoberfest
hamburg
hamkrest
helios
helsinki
hexagon
hibernate
hikari-cp
hire-me
hiring
hongkong
hoplite
http4k
hungary
hyderabad
image-processing
india
indonesia
inkremental
intellij
intellij-plugins
intellij-tricks
internships
introduce-yourself
io
ios
iran
israel
istanbulcoders
italian
jackson-kotlin
jadx
japanese
jasync-sql
java-to-kotlin-refactoring
javadevelopers
javafx
javalin
javascript
jdbi
jhipster-kotlin
jobsworldwide
jpa
jshdq
juul-libraries
jvm-ir-backend-feedback
jxadapter
k2-early-adopters
kaal
kafka
kakao
kalasim
kapt
karachi
karg
karlsruhe
kash_shell
kaskade
kbuild
kdbc
kgen-doc-tools
kgraphql
kinta
klaxon
klock
kloudformation
kmdc
kmm-español
kmongo
knbt
knote
koalaql
koans
kobalt
kobweb
kodein
kodex
kohesive
koin
koin-dev
komapper
kondor-json
kong
kontent
kontributors
korau
korean
korge
korim
korio
korlibs
korte
kotest
kotest-contributors
kotless
kotlick
kotlin-asia
kotlin-beam
kotlin-by-example
kotlin-csv
kotlin-data-storage
kotlin-foundation
kotlin-fuel
kotlin-in-action
kotlin-inject
kotlin-latam
kotlin-logging
kotlin-multiplatform-contest
kotlin-mumbai
kotlin-native
kotlin-pakistan
kotlin-plugin
kotlin-pune
kotlin-roadmap
kotlin-samples
kotlin-sap
kotlin-serbia
kotlin-spark
kotlin-szeged
kotlin-website
kotlinacademy
kotlinbot
kotlinconf
kotlindl
kotlinforbeginners
kotlingforbeginners
kotlinlondon
kotlinmad
kotlinprogrammers
kotlinsu
kotlintest
kotlintest-devs
kotlintlv
kotlinultimatechallenge
kotlinx-datetime
kotlinx-files
kotlinx-html
kotrix
kotson
kovenant
kprompt
kraph
krawler
kroto-plus
ksp
ktcc
ktfmt
ktlint
ktor
ktp
kubed
kug-leads
kug-torino
kvision
kweb
lambdaworld_cadiz
lanark
language-evolution
language-proposals
latvia
leakcanary
leedskotlinusergroup
lets-have-fun
libgdx
libkgd
library-development
lincheck
linkeddata
lithuania
london
losangeles
lottie
love
lychee
macedonia
machinelearningbawas
madrid
malaysia
mathematics
meetkotlin
memes
meta
metro-detroit
mexico
miami
micronaut
minnesota
minutest
mirror
mockk
moko
moldova
monsterpuzzle
montreal
moonbean
morocco
motionlayout
mpapt
mu
multiplatform
mumbai
munich
mvikotlin
mvrx
myndocs-oauth2-server
naming
navigation-architecture-component
nepal
new-mexico
new-zealand
newname
nigeria
nodejs
norway
npm-publish
nyc
oceania
ohio-kotlin-users
oldenburg
oolong
opensource
orbit-mvi
osgi
otpisani
package-search
pakistan
panamá
pattern-matching
pbandk
pdx
peru
philippines
phoenix
pinoy
pocketgitclient
polish
popkorn
portugal
practical-functional-programming
proguard
prozis-android-backup
pyhsikal
python
python-contributors
quasar
random
re
react
reaktive
realm
realworldkotlin
reductor
reduks
redux
redux-kotlin
refactoring-to-kotlin
reflect
refreshversions
reports
result
rethink
revolver
rhein-main
rocksdb
romania
room
rpi-pico
rsocket
russian
russian_feed
russian-kotlinasfirst
rx
rxjava
san-diego
science
scotland
scrcast
scrimage
script
scripting
seattle
serialization
server
sg-user-group
singapore
skia-wasm-interop-temp
skrape-it
slovak
snake
sofl-user-group
southafrica
spacemacs
spain
spanish
speaking
spek
spin
splitties
spotify-mobius
spring
spring-security
squarelibraries
stackoverflow
stacks
stayhungrystayfoolish
stdlib
stlouis
strife-discord-lib
strikt
students
stuttgart
sudan
swagger-gradle-codegen
swarm
sweden
swing
swiss-user-group
switzerland
talking-kotlin
tallinn
tampa
teamcity
tegal
tempe
tensorflow
terminal
test
testing
testtestest
texas
tgbotapi
thailand
tornadofx
touchlab-tools
training
tricity-kotlin-user-group
trójmiasto
truth
tunisia
turkey
turkiye
twitter-feed
uae
udacityindia
uk
ukrainian
uniflow
unkonf
uruguay
utah
uuid
vancouver
vankotlin
vertx
videos
vienna
vietnam
vim
vkug
vuejs
web-mpp
webassembly
webrtc
wimix_sentry
wwdc
zircon
Powered by
Title
c

CLOVIS

04/04/2023, 11:48 AM
In the new website, the page https://arrow-kt.io/learn/typed-errors/working-with-typed-errors/#accumulating-different-computations recommends the pattern of using
operator invoke
to create a constructor-like function. In my opinion, this is an anti-pattern, because it makes code harder to understand and the IDEA integration more confusing for beginners (you have to click on the opening parentheses to go to the source code, not on the function name!). To my knowledge, it's also never used in the standard library or any other official library, which all use top-level functions with the same name as the class to do this (
Array
,
List
, ...).
a

Alejandro Serrano Mena

04/04/2023, 11:49 AM
I’ve used it quite often, so maybe I was biased when writing that part
I think it’s something we can easily fix, the use of such a constructor is not required for the section itself
thanks for your input 🙂
c

CLOVIS

04/04/2023, 11:51 AM
On a more positive note, the article is great
The part on creating custom DSLs, in particular, is eye-opening
m

Marko Novakovic

04/04/2023, 11:59 AM
I’m also used to doing this. As far as I know this is actually used in stdlib and variation of this is very widely used
c

CLOVIS

04/04/2023, 12:01 PM
I'm curious to see if you have an example of it, I never found any. I also never found it mentioned in the official docs. It seems to me that it's an old pattern that a lot of people still use.
s

simon.vergauwen

04/04/2023, 12:01 PM
There is actually two common styles, I've gone back and forth and both are used in Kotlin Std / KotlinX. •
operator fun invoke
fun ClassName(...): ClassName
The only real reason for using the former is that it gives you access to
private constructor
. Otherwise it requires you to make the constructor
internal
. Or you need to define
fun ClassName
on the
Companion
which is also a bit strange 🤔 I do prefer the latter though, after a lot of back-and-forth but I do miss file private support from Scala to overcome the
private constructor
issue.
Actually, since this is a
data class
it doesn't even matter since
copy
can still break the contract. I was going to say the
private constructor
there completely eliminates the ability to constructor incorrect instances... We'll have to wait on multi-field
value class
for that.
c

CLOVIS

04/04/2023, 12:11 PM
I wish
private
on the primary constructor meant private-in-file and not private-in-class, but well
s

simon.vergauwen

04/04/2023, 12:20 PM
Yes, I agree. I agree with your overall assessment though, but I am unsure what the best solution is because now I also feel we need to mention the
copy
caveat 😅 and/or suggest a solution. IIRC there was a compiler-plugin for that, and now I guess two with DataClassGenerate.
j

Javier

04/04/2023, 12:25 PM
I click over parenthesis for normal constructor, and to see instances of that class too 🤔
w

Wilerson Oliveira

04/04/2023, 12:44 PM
Re: the
copy
caveat, one alternative would be to run the checks on
init
, but that would lead to duplication and to throwing, which is probably not desirable
a

asdf asdf

04/04/2023, 12:47 PM
The main issue I have with using
invoke
on a companion object is that it has to be manually imported as intellij doesn’t give auto completion for operator functions (unless there’s a setting I don’t know that changes that)
s

simon.vergauwen

04/04/2023, 12:48 PM
I don't think I've every manually imported
invoke
😮
j

Javier

04/04/2023, 12:48 PM
It works for me automatically
c

CLOVIS

04/04/2023, 12:48 PM
It's been a few years since I last needed to do it manually, but there was definitely a time when it didn't do it automatically
a

asdf asdf

04/04/2023, 2:17 PM
Really? :O
I have got to figure out how to make that work because it would save so much time lol
s

stojan

04/04/2023, 2:23 PM
I think the factory function is the more common approach in Kotlin... e.g.
MutableStateFlow
is a function. from what I remember, the kotlin team does NOT recommend the invoke on companion object because the companion object creates an object in bytecode. for this specific example (the user example of the docs) we can get around the issue (data classes having copy) by using:
@JvmInline value class Age private constructor(val value: Int)
+ factory function (which returns
Either
) 🙂 then
data class User (val name: String, val age: Age)
s

simon.vergauwen

04/04/2023, 3:01 PM
How do you define the factor method there for
Age
without
companion object
and without removing
private
from constructor? :trollface:
s

stojan

04/04/2023, 3:03 PM
yup, you do need the companion with
private constructor
😄 ....
s

simon.vergauwen

04/04/2023, 3:07 PM
The best I've found, and is used by Kotlin(X) in multiple places is.
@JvmInline value class Age private constructor(val value: Int) {
  companion object {
    fun Age(...): Either<Error, Age> = ...
  }
}
It's used by Duration, some KotlinX libraries (datetime?), .. 🤔 Albeit it's also a bit strange. Should we update towards this? It combines the benefits of all I think.
When typing
Age(..
it'll resolve, and automatically add the import
my.pack.Age.Companion.Age
s

stojan

04/04/2023, 3:08 PM
my point with the
Age
example is, that unless properties depend on each other (like openDate should be before closeDate of a bank account) you can typically push the opaque type up, towards the individual properties.... Then copy doesn't break your invariants
s

simon.vergauwen

04/04/2023, 3:11 PM
"soon", I am really hoping we get some clarity on timelines @ KotlinConf. I know K2 is highest priority, and I am happy it's the case because besides languages improvements it'll also bring more stability and IDEA improvements but the timeline after K2 is still unclear to me.
m

mitch

04/05/2023, 11:23 AM
There’s a lot of good things coming. I’m personally really excited about context receivers hopefully that’s going to be finalized sooner rather than later!