Skip to content

g3_timeareadata() naming clash potential #243

@lentinj

Description

@lentinj

Having a g3_timeareadata() with the same name as the stock (e.g.) is both very natural to do if you don't care about the name and creates a big mess.

  • Should we prefix the actual variable with tad_? This would be hard to do without breaking back-compatibility though
  • Add a prefix to the name if there's a clash, rather than choosing one and hoping for the best?
  • Something else?

Like other functions that ask for a name, the user likely doesn't care, and would rather it pick something sensible.

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