Skip to content

Conversation

@DenverM80
Copy link
Contributor

*** No errors detected
==9120==
==9120== HEAP SUMMARY:
==9120== in use at exit: 91,618 bytes in 17 blocks
==9120== total heap usage: 4,660,224 allocs, 4,660,207 frees, 2,942,534,707 bytes allocated
==9120==
...
==9120== LEAK SUMMARY:
==9120== definitely lost: 0 bytes in 0 blocks
==9120== indirectly lost: 0 bytes in 0 blocks
==9120== possibly lost: 0 bytes in 0 blocks
==9120== still reachable: 91,618 bytes in 17 blocks
==9120== suppressed: 0 bytes in 0 blocks
==9120==
==9120== For counts of detected and suppressed errors, rerun with: -v
==9120== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
[100%] Built target mem

LIBRARY_API ds3_error* ds3_verify_safe_to_create_put_job_spectra_s3_request(const ds3_client* client, const ds3_request* request);
LIBRARY_API ds3_request* ds3_init_get_node_spectra_s3_request(const char* resource_id);
LIBRARY_API ds3_request* ds3_init_get_node_spectra_s3_request(const char *const resource_id);
LIBRARY_API ds3_error* ds3_get_node_spectra_s3_request(const ds3_client* client, const ds3_request* request, ds3_node_response** response);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should the client in this case also be const?

@rpmoore rpmoore merged commit 8688b56 into SpectraLogic:master Apr 19, 2017
@DenverM80 DenverM80 deleted the const_correctness branch July 28, 2017 19:25
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

Successfully merging this pull request may close these issues.

2 participants