| 28 Apr 2019 |
|  @zjuhasz:matrix.org invited  Shan. | 15:22:52 |
| Shan joined the room. | 15:23:06 |
| @zjuhasz:matrix.orgchanged room power levels. | 15:24:49 |
| 3 May 2019 |
| @zjuhasz:matrix.org changed their profile picture. | 14:36:56 |
| 18 May 2019 |
|  caseystratton joined the room. | 01:16:29 |
| caseystratton | What ever happened to the density units? I saw in an old project of mine that KILOGRAM_PER_LITER existed, but IDEA can't find it in the latest version (using complete units) | 01:19:03 |
| @zjuhasz:matrix.org | I don't remember that unit. Do you know what version of Physikal you able to use KILOGRAM_PER_LITER from? | 01:40:16 |
| caseystratton | looks like 2.0.1.0 | 01:41:23 |
| caseystratton | i'm guessing you guys are waiting for UoM 2.0 to be released? | 01:41:40 |
| caseystratton | though i saw you were considering rewriting it ground up in kotlin instead of using UoM as a dependency | 01:42:46 |
| @zjuhasz:matrix.org | We will need to do something major for sure because we need Physikal to be multiplatform. I'm hoping we can do it in a way that maintains compatability with Java UoM but it doesn't seem likely at the moment. | 01:44:02 |
| caseystratton | kotlin syntax (extensions and infix especially) definitely makes for better usage of uom | 01:44:12 |
| caseystratton | something like val foo: Density = 3.kg per 1.L sounds totally doable, but i see you are a small team, and i'm guessing this is a pet project | 01:46:05 |
| caseystratton | or val foo = 3.kg/L is also possible in Kotlin. This is all such a cool idea, imo. | 01:47:41 |
| @zjuhasz:matrix.org | Sort of a pet project. We need a units library for https://github.com/Tenkiv/Kuantify (I haven't posted this anywhere even though it's been open source for a while) | 01:47:56 |
| @zjuhasz:matrix.org | There are lots of better things we could do in pure kotlin | 01:48:15 |
| @zjuhasz:matrix.org | I think it should really be based around a compiler plugin | 01:48:38 |
| caseystratton | i just completed my undergrad, and while i'm working on my next stage in life i have some freetime. i might help. | 01:48:45 |
| @zjuhasz:matrix.org | The problem with a compiler plugin is it's not at all stable yet and there is almost no documentation | 01:49:20 |
| @zjuhasz:matrix.org | But we could do really cool things like actually recognise 1m / 1s results in the type Quantity<Speed> at compile time | 01:49:59 |
| caseystratton | yeah, i don't know much at all about that. what would make the compiler plugin better? it sounds difficult to do | 01:50:05 |
| caseystratton | even without compiler, you can get 1.m/s working. | 01:51:17 |
| @zjuhasz:matrix.org | It would mostly be nice for when you're doing math with quantities | 01:51:58 |
| @zjuhasz:matrix.org | like (10m / 5s) -10.m/s | 01:52:41 |
| @zjuhasz:matrix.org | not as compelling in the super simplified examples | 01:52:52 |
| caseystratton | i see | 01:52:59 |
| caseystratton | if i learn anything about compiler plugins, i'll add unbounded ranges to the language ASAP, e.g. val foo = list[..3] | 01:53:47 |
| @zjuhasz:matrix.org | I'm guessing it will be one of the major announcements in Kotlin 1.4 as they already exist but have no stability gaurentees or documentation at the moment | 01:55:08 |
| @zjuhasz:matrix.org | compiler plugins that is | 01:55:31 |
| caseystratton | yeah | 01:55:34 |
