You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
currently, coco has a few packages builtin. but even those are not well made. it needs to be reimplemented, adding support for external packages (including local files) and importing those from web.
import * as io from 'io'
import { floor, round } from 'math'
import { getTime } from './clock'
// for this it will need package manager
import { myVeryOwnValue } from 'my-very-own-first-package'
import { externalObj } from 'https://example.com/external.co'
main goals
more & good stdlib
this one is pretty tricky. all libs (io, math, etc.) can be exported to C dynamic library and used later. we can define those functions and use it in lib object. probably, would add externing via those, but don't know how it would work.
currently, coco has a few packages builtin. but even those are not well made. it needs to be reimplemented, adding support for external packages (including local files) and importing those from web.
main goals
this one is pretty tricky. all libs (io, math, etc.) can be exported to C dynamic library and used later. we can define those functions and use it in lib object. probably, would add externing via those, but don't know how it would work.
dlopen crate, which provides loading cdylibs
Deno way to run FFI code using cdylib
done
import * as name from 'package-name'
import { ... } from 'package-name
The text was updated successfully, but these errors were encountered: