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

Bug - in combining use fo multiple containers in one program unit #156

Open
tclune opened this issue Mar 1, 2022 · 2 comments
Open

Bug - in combining use fo multiple containers in one program unit #156

tclune opened this issue Mar 1, 2022 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@tclune
Copy link
Member

tclune commented Mar 1, 2022

If multiple (v2) containers are used in a single program unit, some of the procedure names conflict. E.g., before begin() was only a type-bound procedure on containers that support iterators. But it is now also a PUBLIC function that takes an iterator as an argument.

I took the easy path and did not use a generic interface block to expose the method which results in unnecessary name conflicts. The correction is to use interface blocks in each case. Tedious, but straightforward.

@tclune tclune added the bug Something isn't working label Mar 1, 2022
@weiyuan-jiang
Copy link
Contributor

I would like your help to explain to me the structure of gFTL

@tclune
Copy link
Member Author

tclune commented Mar 2, 2022

ok - maybe we can do this after the SI meeting today. Might be easier if we can point at a shared screen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants