-
Notifications
You must be signed in to change notification settings - Fork 40
Kotlin/Native support #104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
No review - but this is epic! |
|
What does the integration story look like? e.g. is this a usable API for Swift or C++? |
|
Not sure, that it will be easy to use it there because of suspend functions, but it possible, you can read it here:
|
f7e0943 to
2ea6f4a
Compare
|
PR is ready for review, but some changes in tests running on CI will land soon. As for now, some tests are running too long on CI |
|
|
||
| suspend fun main() { | ||
| val api = connectToApi("Yuri") | ||
| val api = connectToApiUsingWS("Yuri") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks... I guess.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hah, yes, just first name which comes in mind after mine :)
yschimke
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Review didn't seem too bad, mainly
- build setup changes
- TCP duplex connection using supported channels etc.
- IntMap rewrite
654d043 to
18994d6
Compare
28ef408 to
561fa9b
Compare
Reworked TCP implementation Multiplatform Synchronized IntMap implementation
561fa9b to
03af77c
Compare
IntMapimplementation based on NettyIntObjectHashMap- on K/N it uses atomics to support modification, even if it's freezed. Implementation is synchronized, so it's possible to use it concurrently.Should work with WS on K/N when ktor will support it (may be in 1.5.0).
Tests for almost all targets are running ~ 1 hour, except for tvos and watchos (up to 3 hours), where new K/N allocator isn't supported (yet?).