-
Notifications
You must be signed in to change notification settings - Fork 193
Hashmap test update #1025
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
base: master
Are you sure you want to change the base?
Hashmap test update #1025
Conversation
This is a refactor of the main hashmap test routine to improve coverage and simplify the code. The fypp preprocessor directives have been removed to make the code easier to work with and modify for future releases.
Addressed 132 character limit issues.
Minor cleanup
Add example of using abstract hashmap_type for procedure interrface.
This PR also makes the abstract hashmap_type public so that can be used for interface definition that works for both open and chaining types. I thought it was worth adding a simple example showing the use of that. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @chuckyvt for this PR. Overall it looks good to me. I have only minor suggestions
! This allows the procedure to be used for both chaining and open hashmap types. | ||
|
||
program example_abstract_type | ||
use stdlib_kinds, only: int8, int64 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
use stdlib_kinds, only: int8, int64 |
Both are not used in this example
@@ -0,0 +1,53 @@ | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice suggestion to make hashmap_type
public
Could you update the specs, too, please?
As part of development work on the stdlib hashmaps, I have run into CI failures on the stdlib test that I'm not sure if it's due to code updates, or because of format of hashmap test program. For example, the way the current implantation uses transfer to generate character values, I'm not sure it's always generating valid character values. Also fypp makes it harder to develop and update the test routine as the hashmaps evolve.
This PR is an attempt to address those shortcomings. The intent is to improve test coverage of hashmap functions, improve test quality (ensure valid data is being used for key and values), and simplify the code and remove fypp preprocessor format.