Skip to content

Instantly share code, notes, and snippets.

@andrcmdr

andrcmdr/kotlinask_13.kt.txt

Last active December 16, 2018 00:47
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save andrcmdr/d857617efdfb4ca4520c0cee4ad2f497 to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save andrcmdr/d857617efdfb4ca4520c0cee4ad2f497 to your computer and use it in GitHub Desktop.
Download ZIP

Revisions

  1. andrcmdr revised this gist Dec 16, 2018. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion kotlinask_13.kt.txt
    View file
    Original file line number Diff line number Diff line change
    @@ -4,7 +4,7 @@ Here some questions for #kotlinask_13 about #Kolin features:

    ⦁ Possibilities of applying project Loom and using of JVM fibers for Kotlin coroutines and suspend functions (for optimisation purposes maybe) in the future

    ⦁ Possibilities and abilities of writing (preemptive) thread dispatcher/scheduler/monitor for coroutines management, i.e. M:N mapping pool of coroutines (concurrent fibers) to thread-pool of system threads - for Kotlin/JVM and Kotlin/Native
    ⦁ Possibilities and abilities of writing (preemptive) thread dispatcher/scheduler/monitor for coroutines management, i.e. M:N mapping pool of concurrent fibers (coroutines) to thread-pool of system threads - for Kotlin/JVM and Kotlin/Native

    ⦁ Garbage collecting and reference counting (ARC?) mechanisms/algorithms in Kotlin/Native - possible overhead

  2. andrcmdr revised this gist Dec 16, 2018. 1 changed file with 5 additions and 5 deletions.
    10 changes: 5 additions & 5 deletions kotlinask_13.kt.txt
    View file
    Original file line number Diff line number Diff line change
    @@ -1,18 +1,18 @@
    Here some questions for #kotlinask_13 about #Kolin features:

    ⦁ Possibilities of compiling Kotlin/JVM code (with using of Vert.x project, for ex.) with GraalVM/SubstrateVM AoT Compiler - possible overhead
    ⦁ Possibilities of compiling Kotlin/JVM code (with using of Vert.x project, for example) with GraalVM/SubstrateVM AoT Compiler - possible time/memory overhead during compile-time phase

    ⦁ Possibilities of applying project Loom JVM fibers for Kotlin coroutines and suspend functions in the future
    ⦁ Possibilities of applying project Loom and using of JVM fibers for Kotlin coroutines and suspend functions (for optimisation purposes maybe) in the future

    ⦁ Possibilities and abilities of writing (preemptive) thread dispatcher/scheduler/monitor for coroutines management and (M:N) mapping of coroutines to thread-pool of system threads - for Kotlin/JVM and Kotlin/Native
    ⦁ Possibilities and abilities of writing (preemptive) thread dispatcher/scheduler/monitor for coroutines management, i.e. M:N mapping pool of coroutines (concurrent fibers) to thread-pool of system threads - for Kotlin/JVM and Kotlin/Native

    ⦁ Garbage collecting and reference counting (ARC?) mechanisms/algorithms in Kotlin/Native - possible overhead

    ⦁ WASM codegen support in Kotlin/Native and memory management compatibility between Kotlin/Native and WASM run-times, possibilities of convergence with Kotlin/JS in the future

    ⦁ Possibilities of RAII (scope based) and manual memory management without automatic GC w/RC in Kotlin/Native, how to use raw and safe pointers/references in Kotlin/Native
    ⦁ Possibilities of RAII (scope based memory management, scope guards, destructors and control of lifetimes of memory objects) and manual memory management without automatic (cyclic/tracing) GC w/RC in Kotlin/Native, how to use raw and safe pointers/references in Kotlin/Native

    ⦁ Possibilities of memory safery and thread safety in Kotlin/Native - control immutability of pointers & references, strong/weak references (ARC), reference types and value types (off-heap data types), stack memory management and stack safety
    ⦁ Possibilities of memory safery and thread safety in Kotlin/Native - control immutability of pointers & references, i.e. strong/weak references (ARC) and heap memory management, reference types and value types (off-heap data types), stack memory management and stack safety (something similar like borrowing and borrow checker in Rust)

    ⦁ Possibilities of support for UFCS (Uniform Function Call Syntax - https://en.wikipedia.org/wiki/Uniform_Function_Call_Syntax) in Kotlin future releases

  3. andrcmdr revised this gist Dec 4, 2018. 1 changed file with 1 addition and 3 deletions.
    4 changes: 1 addition & 3 deletions kotlinask_13.kt.txt
    View file
    Original file line number Diff line number Diff line change
    @@ -1,6 +1,4 @@
    ###Here some questions we have for #kotlinask_13 about #Kolin features:

    https://gist.github.com/andrcmdr/d857617efdfb4ca4520c0cee4ad2f497
    Here some questions for #kotlinask_13 about #Kolin features:

    ⦁ Possibilities of compiling Kotlin/JVM code (with using of Vert.x project, for ex.) with GraalVM/SubstrateVM AoT Compiler - possible overhead

  4. andrcmdr revised this gist Dec 4, 2018. 1 changed file with 4 additions and 2 deletions.
    6 changes: 4 additions & 2 deletions kotlinask_13.kt.txt
    View file
    Original file line number Diff line number Diff line change
    @@ -1,4 +1,6 @@
    Here some questions for #kotlinask_13 about #Kolin features:
    ###Here some questions we have for #kotlinask_13 about #Kolin features:

    https://gist.github.com/andrcmdr/d857617efdfb4ca4520c0cee4ad2f497

    ⦁ Possibilities of compiling Kotlin/JVM code (with using of Vert.x project, for ex.) with GraalVM/SubstrateVM AoT Compiler - possible overhead

    @@ -8,7 +10,7 @@ Here some questions for #kotlinask_13 about #Kolin features:

    ⦁ Garbage collecting and reference counting (ARC?) mechanisms/algorithms in Kotlin/Native - possible overhead

    ⦁ WASM codegen support in Kotlin/Native and memory management compatibility between them
    ⦁ WASM codegen support in Kotlin/Native and memory management compatibility between Kotlin/Native and WASM run-times, possibilities of convergence with Kotlin/JS in the future

    ⦁ Possibilities of RAII (scope based) and manual memory management without automatic GC w/RC in Kotlin/Native, how to use raw and safe pointers/references in Kotlin/Native

  5. andrcmdr revised this gist Dec 4, 2018. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion kotlinask_13.kt.txt
    View file
    Original file line number Diff line number Diff line change
    @@ -14,5 +14,5 @@ Here some questions for #kotlinask_13 about #Kolin features:

    ⦁ Possibilities of memory safery and thread safety in Kotlin/Native - control immutability of pointers & references, strong/weak references (ARC), reference types and value types (off-heap data types), stack memory management and stack safety


    ⦁ Possibilities of support for UFCS (Uniform Function Call Syntax - https://en.wikipedia.org/wiki/Uniform_Function_Call_Syntax) in Kotlin future releases

  6. andrcmdr revised this gist Dec 4, 2018. 2 changed files with 18 additions and 17 deletions.
    17 changes: 0 additions & 17 deletions kotlinask_13.kt
    View file
    Original file line number Diff line number Diff line change
    @@ -1,17 +0,0 @@
    Here some questions for #kotlinask_13 about #Kolin features:

    Possibilities of compiling Kotlin/JVM code (with using of Vert.x project, for ex.) with GraalVM/SubstrateVM AoT Compiler - possible overhead

    Possibilities of applying project Loom JVM fibers for Kotlin coroutines and suspend functions in the future

    Possibilities and abilities of writing (preemptive) thread dispatcher/scheduler/monitor for coroutines management and (M:N) mapping of coroutines to thread-pool of system threads - for Kotlin/JVM and Kotlin/Native

    Garbage collecting and reference counting (ARC?) mechanisms/algorithms in Kotlin/Native - possible overhead

    WASM codegen support in Kotlin/Native and memory management compatibility between them

    Possibilities of RAII (scope based) and manual memory management without automatic GC w/RC in Kotlin/Native, how to use raw and safe pointers/references in Kotlin/Native

    Possibilities of memory safery and thread safety in Kotlin/Native - control immutability of pointers & references, strong/weak references (ARC), reference types and value types (off-heap data types), stack memory management and stack safety

    Possibilities of support for UFCS (Uniform Function Call Syntax - https://en.wikipedia.org/wiki/Uniform_Function_Call_Syntax) in Kotlin future releases
    18 changes: 18 additions & 0 deletions kotlinask_13.kt.txt
    View file
    Original file line number Diff line number Diff line change
    @@ -0,0 +1,18 @@
    Here some questions for #kotlinask_13 about #Kolin features:

    ⦁ Possibilities of compiling Kotlin/JVM code (with using of Vert.x project, for ex.) with GraalVM/SubstrateVM AoT Compiler - possible overhead

    ⦁ Possibilities of applying project Loom JVM fibers for Kotlin coroutines and suspend functions in the future

    ⦁ Possibilities and abilities of writing (preemptive) thread dispatcher/scheduler/monitor for coroutines management and (M:N) mapping of coroutines to thread-pool of system threads - for Kotlin/JVM and Kotlin/Native

    ⦁ Garbage collecting and reference counting (ARC?) mechanisms/algorithms in Kotlin/Native - possible overhead

    ⦁ WASM codegen support in Kotlin/Native and memory management compatibility between them

    ⦁ Possibilities of RAII (scope based) and manual memory management without automatic GC w/RC in Kotlin/Native, how to use raw and safe pointers/references in Kotlin/Native

    ⦁ Possibilities of memory safery and thread safety in Kotlin/Native - control immutability of pointers & references, strong/weak references (ARC), reference types and value types (off-heap data types), stack memory management and stack safety


    ⦁ Possibilities of support for UFCS (Uniform Function Call Syntax - https://en.wikipedia.org/wiki/Uniform_Function_Call_Syntax) in Kotlin future releases
  7. andrcmdr created this gist Dec 4, 2018.
    17 changes: 17 additions & 0 deletions kotlinask_13.kt
    View file
    Original file line number Diff line number Diff line change
    @@ -0,0 +1,17 @@
    Here some questions for #kotlinask_13 about #Kolin features:

    Possibilities of compiling Kotlin/JVM code (with using of Vert.x project, for ex.) with GraalVM/SubstrateVM AoT Compiler - possible overhead

    Possibilities of applying project Loom JVM fibers for Kotlin coroutines and suspend functions in the future

    Possibilities and abilities of writing (preemptive) thread dispatcher/scheduler/monitor for coroutines management and (M:N) mapping of coroutines to thread-pool of system threads - for Kotlin/JVM and Kotlin/Native

    Garbage collecting and reference counting (ARC?) mechanisms/algorithms in Kotlin/Native - possible overhead

    WASM codegen support in Kotlin/Native and memory management compatibility between them

    Possibilities of RAII (scope based) and manual memory management without automatic GC w/RC in Kotlin/Native, how to use raw and safe pointers/references in Kotlin/Native

    Possibilities of memory safery and thread safety in Kotlin/Native - control immutability of pointers & references, strong/weak references (ARC), reference types and value types (off-heap data types), stack memory management and stack safety

    Possibilities of support for UFCS (Uniform Function Call Syntax - https://en.wikipedia.org/wiki/Uniform_Function_Call_Syntax) in Kotlin future releases