Hacker News
new
|
past
|
comments
|
ask
|
show
|
jobs
|
submit
login
ominous_prime
on May 7, 2015
|
parent
|
context
|
favorite
| on:
Go crypto: bridging the performance gap
No, the slow part is switching stacks, and coordinating with the scheduler. Go's GC doesn't yet move memory, and even so there will probably be allowances for passing pointers from Go to C when it is implemented.
andrewchambers
on May 7, 2015
[–]
The stacks currently get copied when they run out of space, that may break things already.
Guidelines
|
FAQ
|
Lists
|
API
|
Security
|
Legal
|
Apply to YC
|
Contact
Search:
