yes but I don’t think you can have the same code for a GC available platform and a “manage the memory yourself” platform

or as the blog post say, it woudl require to wrote a common module with platform specific implementation, which would require a lot of time and a lot of missing feature

on the mission part :

Note that we do not intend to make arbitrary Kotlin/JVM programs runnable on Kotlin/Native or Kotlin/JS. It would be equivalent to implementing another JVM, which is both a lot of work and a lot of limitations for the runtime. We are going another way: providing a common language for all platforms while enabling creation of common libraries through seamless interoperability with platform code.

If it doesn't... The stdlib is going to be a very limiting factor. What happens to langs with poor stdlib is they usually suffer pretty badly

See also c++ and the massive amount of time many apps waste on converting between various implementations of String, all because the stdlib has a useless string implementation

Probably for it to be competitive kotlin native would have to at least provide whatever swift provides. Or it will be the odd man out in terms of modern native languages

Looks like the Swift stdlib is pretty big (data structures mostly), but things like Random get pulled from Darwin module I guess (arc4_random)

Maybe it's time for an extended stdlib, which would avoid bloating the current stdlib for platforms like Android?

Actually I was suprised I didn't find

Random

alias and wrappers in stdlib. I'm using

Collections.shuffle(MutableList, Random): Unit

. Of course made and extension

List.shuffled(Random): List

I was hoping to quickly try this project with K/N.

Here’s the corresponding change request for your pleasure: https://youtrack.jetbrains.com/issue/KT-17261

will you add Cmake or any other build system? Gradle makes building really slow no matter the project, java, kotlin or kotlin native, i always avoid it

I guess it mostly depends on the build system itself rather then kotlin-native no?

You can use CLI compiler from whatever build system you need. Gradle is more about integrating into IDE, multiplatform projects, etc.

For now this is correct, no IO or sockets or threading in Kotlin Native stdlib yet

OK good to know that I didn't get it wrong. Thanks!

i'll copy the build.sh script from the repo 😛

@dan_ has left the channel

Haven't dug too deep yet, but why is a GCC toolchain downloaded as a dependency along with LLVM? 2 replies I have and use the LLVM toolchain on Linux just fine, though. 🙂

ok nm my answer was right there in @orangy ‘s response..

Anybody in here?

is there a good networking library for native? 1 reply but take a look at lbcurl example in here https://github.com/JetBrains/kotlin-native/blob/master/samples/libcurl/src/org/konan/libcurl/Program.kt

@mishugana yep

I keep getting an error back from the linker

ld: symbol(s) not found for architecture x86_64

in the build script I added linkerOpts

-Lpath/to/compiled/lib.o

and header

and compiled the lib with

clang -c -target x86_64 test_lib.c

Hello, folks

Does anybody have a paper/blog/article about memory management in kotlin native? I haven't worked much with Kotlin - just dabbled a bit a year or so back, but kotlin native has sparked my interest

There is “Memory management” paragraph in official blog post about K/N https://blog.jetbrains.com/kotlin/2017/04/kotlinnative-tech-preview-kotlin-without-a-vm/