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

What needs to be done? #17

Closed
Eh2406 opened this issue Nov 20, 2017 · 4 comments
Closed

What needs to be done? #17

Eh2406 opened this issue Nov 20, 2017 · 4 comments

Comments

@Eh2406
Copy link

Eh2406 commented Nov 20, 2017

What is left on the todo list to get this useable? What can developers with different backgrounds do to help?

@aldanor
Copy link
Owner

aldanor commented Nov 24, 2017

Hi @Eh2406, apologies, I haven't had much time recently due to heavy involvement with a few other projects, but it's been on my mind to bring this to usable state (especially with the fact that rust-ndarray reached a fairly useful state lately) -- I've mentioned a few things in #14. One question is how to deal with dataset datatypes (mentioned there).

I've just pushed an existing branch I've had, with the latest work -- 4429b00 -- changing trait-based inheritance to specializations; while it's a lot cleaner code-wise and doesn't require end-user to import a million different traits, almost all documentation basically just disappears (due to issues in rustdoc mentioned in #14). (would also appreciate if anyone voiced a thought on whether specializations are indeed better than a multitude of traits; to me personally it looks a lot better)

Fixing the aforementioned rustdoc issue or somehow helping the core team with that would probably be the greatest help of all; or figuring and implementing an alternative way (like in rust-xcb) to generate the docs give there's a lot of aliases and specializations (there's a few other projects that have to ditch rustdoc because of the same reason; which is more of a hack/workaround and more painful to maintain, but it is what it is).

Cheers!

@Eh2406
Copy link
Author

Eh2406 commented Nov 30, 2017

I spent some time trying to use the new branch, and I can confirm that it is not easy to grock from the docs as they are. :-P Perhaps some examples reading and writing with different types could help paper over what rust-doc refuses to render and give some context on how the parts fit together. Some of the confusion is my background, I have only used hdf's from pandas, so if the concepts map to the c-api then I'd miss the connection. Perhaps some links to comparable parts of other languages api's could help?

What practically would be involved in doing the docs the way rust-xcb does it? I looked at the the xcb project but could not find exactly what you are referring to. I also wonder if the new include external files in documentation (RFC 1990) could be used to cover this?

@bluss
Copy link

bluss commented Jan 17, 2018

@aldanor Nice work. I'm very interested in how to design a rust library/program that keeps track of a "foreign" set of data types, in a dynamic way. Thanks for sharing your work, I'll read through it. 😄

@Enet4 Enet4 mentioned this issue Dec 11, 2018
@aldanor
Copy link
Owner

aldanor commented Dec 26, 2018

Closing this since I've recently resumed working on the crate with hopes to make a stable usable release in the foreseeable future.

@aldanor aldanor closed this as completed Dec 26, 2018
This issue was closed.
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

3 participants