Skip to content

Use explicit imports, not using FASTX #17

@jakobnissen

Description

@jakobnissen

Writing using FASTX (or any other package) is bad for two reasons:

  • If FASTX in a new version exports a new name, it may conflict with an existing names in ReadDatastores, causing an error. This means that even adding new features to FASTX can break this package
  • It makes it harder to find the definition the used functions

All of these should be replaced with using FASTX: Foo, Bar, baz, or, if FASTX internals is used, using FASTX: FASTX, Foo, Bar, baz, such that e.g. FASTX.qux can be accessed.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions