Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Code reorganisation and file naming #11

Closed
pinpox opened this issue Dec 9, 2016 · 1 comment
Closed

Code reorganisation and file naming #11

pinpox opened this issue Dec 9, 2016 · 1 comment

Comments

@pinpox
Copy link
Contributor

pinpox commented Dec 9, 2016

After issue #8 I though this might be a point to bring up.

How would you go about the naming of the files and distributing the code in them? I suppose the "general" stuff that applies to any array type would go into numgo.go. For the Arrayb-specific methods we have bool.go. Where would you like the Array64-specific code?

It might be clearer to just have

  • numgo.go: General stuff applying to any array type
  • array64.go: A new file that holds Array64-specific code
  • arrayb.go: bool.go renamed, containing Arrayb-specific code.

Just an idea, I'm open for any other suggestions

@Kunde21
Copy link
Owner

Kunde21 commented Dec 15, 2016

Sound good. We could use nDim.go instead of numgo.go so users don't expect anything special in the file named the same as the package.

This can be incorporated into #10 easily.

@Kunde21 Kunde21 closed this as completed Mar 9, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants