Skip to content
This repository has been archived by the owner on May 4, 2019. It is now read-only.

Things we should deprecate for consistency with Base #239

Open
6 of 9 tasks
ararslan opened this issue Mar 8, 2017 · 2 comments
Open
6 of 9 tasks

Things we should deprecate for consistency with Base #239

ararslan opened this issue Mar 8, 2017 · 2 comments

Comments

@ararslan
Copy link
Member

ararslan commented Mar 8, 2017

In the interest of having an API consistent with that of Base, I think we should deprecate the following methods:

These functions don't really seem to belong here:

Functions that could use more descriptive names:

  • gl (may not belong here though a case could be made)

Thoughts?

@nalimilan
Copy link
Member

+1, but I would say our priority should be to get DataFrames working on 0.6 first. Else there's little point in having a clean API that cannot be used. :-)

@ararslan
Copy link
Member Author

ararslan commented Mar 8, 2017

@nalimilan Definitely. These are just things I came across while doing #238 and I figured I'd note them somewhere so that I don't forget. 🙂

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants