Skip to content

No const qualifiers using htscodecs API. #151

Description

@rhpvorderman

I am currently using the htscodecs library to create python bindings for it because I am interested in using the codecs in contexts outside of CRAM and htslib in an easy plug and play kind of fashion. Python also works well for experimenting a bit.

I found that in the codecs there are no const qualifiers on input data. Python objects are immutable mostly, so the compiler warns me about throwing these pointers into functions without const qualifiers. I assume input data is not changed, but is that the case? Is it sometimes used as a buffer to do things?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions