haskey edge cases about hdf5.jl HOT 5 OPEN

julia> haskey(f, "./aa")
false

This does not throw an error, but perhaps it should be true?

julia> HDF5.API.h5l_exists(f, "./aa", HDF5.API.H5P_DEFAULT)
true

julia> HDF5.API.h5l_exists(f, "aa//", HDF5.API.H5P_DEFAULT)
true

julia> HDF5.API.h5l_exists(f, "bb//cc", HDF5.API.H5P_DEFAULT)
true

julia> HDF5.API.h5l_exists(f, "aa/c", HDF5.API.H5P_DEFAULT)
ERROR: HDF5.API.H5Error: Cannot determine whether aa/c exists
...

Should "aa/c" not error? It does not exist.

from hdf5.jl.

Should "aa/c" not error? It does not exist.

I would say it should return false.

from hdf5.jl.

In #978 and #979, I'm expanding and updating the low level H5O bindings, which seem relevant here based on the h5py code.

from hdf5.jl.

At the end of the loop, it looks like we will need API.h5o_get_info_by_name to check if the object is a group before iterating again.

We will need to write a high level hdf5type function that abstracts over the different h5o_get_info_by_name versions (1 vs 3). For version 3, we can use H5O_INFO_BASIC as the fields argument.

from hdf5.jl.

Here's a link to has_key in this code base. The function is recursive rather than iterative.

from hdf5.jl.