<https viktor sirotin medium com kotunil si units kotlin par kotlinlang #datascience

Channels

kotlin-foundation

compose-android

ohio-kotlin-users

kotlin-by-example

sofl-user-group

kotlin-multiplatform-contest

tricity-kotlin-user-group

kotlin-in-action

android-databinding

cincinnati-user-group

fluid-libraries

codemash-precompiler

kotlingforbeginners

jhipster-kotlin

prozis-android-backup

realworldkotlin

graviton-browser

spring-security

domain-driven-design

connect-audit-events

swiss-user-group

effectivekotlin

refactoring-to-kotlin

russian-kotlinasfirst

androidgithubprojects

introduce-yourself

pocketgitclient

effective-kotlin

algolialibraries

lambdaworld_cadiz

intellij-tricks

kotlin-pakistan

navigation-architecture-component

strife-discord-lib

machinelearningbawas

leedskotlinusergroup

stayhungrystayfoolish

kotest-contributors

practical-functional-programming

swagger-gradle-codegen

100daysofkotlin

kotlinultimatechallenge

pattern-matching

kotlinforbeginners

competitive-programming

compose-ui-showcase

competitivecoding

kotlin-data-storage

skia-wasm-interop-temp

java-to-kotlin-refactoring

event21-community-content

androidx-xprocessing

embedded-kotlin

fb-internal-demo

image-processing

myndocs-oauth2-server

kotlintest-devs

beepiz-libraries

kotlinprogrammers

cscenter-course-2016

k2-early-adopters

intellij-plugins

language-proposals

library-development

refreshversions

language-evolution

kotlinx-datetime

framework-elide

compose-desktop

jvm-ir-backend-feedback

android-architecture

100daysofkotlin-2021

github-workflows-kt

python-contributors

squarelibraries

arrow-contributors

codingconventions

getting-started

Title

v

Viktor Sirotin

01/28/2023, 4:17 PM

https://viktor-sirotin.medium.com/kotunil-si-units-kotlin-part-one-introduction-to-kotunil-3b5add3e7acc

a

altavir

01/28/2023, 5:51 PM

Just for the record, there was a previous much more simple attempt here: https://github.com/nacular/measured

My main concern for this library is scope pollution. Wouldn't it be better to define a scope for those extensions? It would require context receivers for full flexibility, but since they are on the table, it makes sense to use it.

v

Viktor Sirotin

01/28/2023, 5:58 PM

You are right. nacular/mesuared is relatively simple bibliotek. Requirements for KotUniL are much more extensive.

Could you please to explain your idea with receivers?

a

altavir

01/28/2023, 6:01 PM

Another reason to use scopes is the same reason we use algebra scopes in KMarth - the treatment of units is slightly different in different domains. I use different type-safe units in different projects.

The idea is that you define your extensions not globally like

Number.m

, but inside specific scope like

context(TypeSafeUnitsScope) Number.m

. You can do it without context receivers by creating member extensions for the object or class, but it will limit extensibility. because you will have to extend class to add new units. Context receivers solve this problem.

v

Viktor Sirotin

01/28/2023, 6:30 PM

To be honest, I believe, that context receivers should be used in very special, very rare domains. The possible problem of scope popylation by using of KotUniL can be solved with intelligently using of imports, IMHO. Nevertheless, thank you for your suggestion. I will think about it further.

6 Views

#datascience Join Slack