Change module/package loading to include the extension about odotdot HOT 5 OPEN

If I have a lol.ö library and I want to add more files, I need to break backwards compatibility by forcing people to import "lol/somefile.ö".

from odotdot.

sidebar:

I think a question to answer before that is how would importing a directory work?

x.odotdot
lol/
  |-- <somename>.odotdot
  |-- file1.odotdot
  |-- file2.odotdot
  `-- file3.odotdot

I want to import all of lol

should <somename>.odotdot be __init__.odotdot or _.odotdot or even just .odotdot

to import, "./lol", "./lol/", "./lol/<somename>.odotdot", or something else?

from odotdot.

I think the backwards compatibility story can be solved by the package maintainer having a stub lol.ö that points to lol/somefile.ö

in that case its just the same as maintaining any API, keep things in the old places which wrap the new underlying code

from odotdot.

<somename>: could be probably something like exports

stub files: might be confusing, i like your point about how it doesn't differ much from other api maintaining, maybe it's a good idea after all

which import string: i had thought of (import "./lol"), where the ./ is optional because it always imports relative to current file unless the import starts with <std>

from odotdot.

1 more reason why having .ö at the end of the import would be good:

$ grep -r shit.ö   # where is this garbage used?

from odotdot.