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
j

Jérémy Touati

07/27/2019, 6:18 PM
hello there, very new to Kotlin (as in, I've started today), and I'm trying to find the way to have a secondary constructor work out in the following scenario: consider a chess board position that can be represented either through (x, y) coordinates (as a multidimensional array would), or as a string such as "B4"
class Position(val x: Int, val y: Int) {
	constructor(positionCode: String) {
		// construct a position from code here
	}
}
this yields an error as the secondary constructor must call the primary one with
: this(...)
i don't see an easy way to achieve this, i could call a function in the parent call such as
this(getCoordsFromCode(positionFromCode))
but it obviously won't work as the primary one expects two ints, and I don't think you can unpack an array into a function that isn't expecting vararg i could obviously swap the constructors and have the parent constructor call be something like
this(getCodeFromCoords(x, y))
, but I was wondering if I was missing something (and I'm pretty sure I am)
m

Mark Murphy

07/27/2019, 6:27 PM
You could use a
companion object
and a factory function:
class Position(val x: Int, val y: Int) {
    companion object {
        fun fromCode(positionCode: String): Position {
            // construct a position from code here
        }
    }
}
You can then call
Position.fromCode()
to create a
Position
given a position code.
a

Adam Powell

07/27/2019, 6:29 PM
Or write the factory function like an "extension constructor." If you declare a top-level function with the same name as the class, you can invoke it with the same syntax as a constructor call:
fun Position(positionCode: String): Position {
  // parse the position code
  return Position(x, y)
}

class Position(val x: Int, val y: Int) {
  // other class contents
}
and also avoid taking dependencies on unrelated "constructor" parameter types or parsing formats in a class's core implementation
j

Jérémy Touati

07/27/2019, 6:30 PM
@Mark Murphy exactly what I ended up doing, but was still curious if there was a way with pure constructor overloading @Adam Powell oh that's pretty nifty, is that considered good practice? no particular downsides to it?
a

Adam Powell

07/27/2019, 6:31 PM
It's used in a number of libraries like
kotlinx.coroutines
for
Job()
j

Jérémy Touati

07/27/2019, 6:32 PM
good to know! thanks to you both
a

Adam Powell

07/27/2019, 6:34 PM
the downsides to it are that sometimes there are better/more idiomatic solutions in particular situations
m

Mark Murphy

07/27/2019, 6:34 PM
for the pure-constructor approach, I think that you would need to use
this(getXFromCode(positionCode), getYFromCode(positionCode))
, requiring two parsing passes, which isn't ideal
a

Adam Powell

07/27/2019, 6:35 PM
if the parameters don't vary by type you'll probably want something with a more descriptive name. Regular top-level factory functions work well there, but compete with the companion object style in terms of discoverability - java developers are used to typing
Typename.
to get an autocomplete list of options.
see things like
listOf()
for an example of that
and if you're taking only a single parameter that you're converting from or decorating,
fun Foo.toBar(): Bar
or
fun Foo.asBar(): Bar
is more idiomatic, respectively
and yeah to @Mark Murphy’s point, if you want a primary constructor you're left double-parsing or alternatively, declaring all of your constructors as secondary constructors java-style
but kotlin in general strongly encourages small classes and decoupled extensions written to classes' public api surface
j

Jérémy Touati

07/27/2019, 7:04 PM
@Adam Powell can you elaborate on "if the parameters don't vary by type you'll probably want something with a more descriptive name" -> what do you mean by "don't vary by type?" also, shouldn't the autocomplete still discover companion object's methods even if with a toplevel factory function defined?
a

Adam Powell

07/27/2019, 7:05 PM
If you have a top level factory function it by definition isn't part of the companion object to find it there 🙂
and if you had two different string formats to parse you'd have two functions that each take a string as a parameter, and they'd have to have different names. You couldn't just use the class name and treat them like constructors. Same problem you'd have with normal constructors too.
j

Jérémy Touati

07/27/2019, 7:06 PM
oh, sure but i mean, in the current example, if I type
Position.
, I'm not expecting to find a top level function as a suggestion
a

Adam Powell

07/27/2019, 7:08 PM
developers new to kotlin sometimes don't think to look for top-level functions or
.toFoo()
extensions; it's temporary as an audience learns the language but something to occasionally consider.
j

Jérémy Touati

07/27/2019, 7:12 PM
right thanks again for all this valuable input