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

fefgGet - do we need it, really? #43

Open
wandell opened this issue Dec 5, 2014 · 0 comments
Open

fefgGet - do we need it, really? #43

wandell opened this issue Dec 5, 2014 · 0 comments

Comments

@wandell
Copy link
Collaborator

wandell commented Dec 5, 2014

We should have a discussion about why we absolutely need to have fgGet and fefgGet. I know this seemed important to FP. It makes the code organization much harder to follow - why is there an fg and also an fg that is specialized to the fe context. If we can reorganize to eliminate the two types of fg gets, many good things will follow (IMO).

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

1 participant