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
There should only be one single import function that, depending on the format of the import path (and potentially other options) decides what to import from where.
One possible idea would look as follows:
Module (qualified name — unqualified names are no longer supported):
This would require the existence of a “provider” service github that knows how to locate, load (and cache?) modules from that source. This last point might become complicated once versioning is involved.
This might also incorporate version specifiers (e.g. by adding a suffix of the form >='1.0.0', or @'rev'). See #28.
Yes, these are all unquoted. stringly typing is verboten. I’m as yet undecided whether the final version will support quoted specifications at all — probably not. Similarly, I’m not sure yet whether tidyeval support is desirable, but import_ will probably die.
The text was updated successfully, but these errors were encountered:
There should only be one single
import
function that, depending on the format of the import path (and potentially other options) decides what to import from where.One possible idea would look as follows:
Module (qualified name — unqualified names are no longer supported):
Package:
Module from external source:
This would require the existence of a “provider” service
github
that knows how to locate, load (and cache?) modules from that source. This last point might become complicated once versioning is involved.This might also incorporate version specifiers (e.g. by adding a suffix of the form
>='1.0.0'
, or@'rev'
). See #28.Yes, these are all unquoted. stringly typing is verboten. I’m as yet undecided whether the final version will support quoted specifications at all — probably not. Similarly, I’m not sure yet whether tidyeval support is desirable, but
import_
will probably die.The text was updated successfully, but these errors were encountered: