-
-
Notifications
You must be signed in to change notification settings - Fork 48
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
Any particular reason why ss and rs are not exported #64
Comments
The reasoning behind this is mostly a game theory thing. The The main reasoning behind the Not exposing the internal concrete structures was basically a way to enforce that a proper think through is required when using slices. For example, in a logic programming language I created using package Furthermore, exposing the internal concrete type that implements Slice would simply add to the confusion - e.g. why are there so many types of notion of slice!? Now, I will admit that this causes usability issues - if you have to reimplement the interface every time it would be very inconvenient! I'm open to suggestions - the best suggestion so far was that we should have another package - a Another suggestion is something like gorgonia.S which simply exports Happy to hear your thoughts. @standy66 |
Hi!
I would like to use this library for tensor manipulations in Golang. Is there any reason as to why range slices and single element slices are not exported in slice.go? It would be very convenient if they were exported, e.g. like this:
The text was updated successfully, but these errors were encountered: