Improve lsm_str
API #17
Labels
No Label
Kind/Bug
Kind/Enhancement
Kind/Feature
Project/Lander
Project/Landerctl
idea
invalid
question
wontfix
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Chewing_Bever/lander#17
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
The current design for
lsm_str
is turning out to be rather cumbersome to use. Therefore I think the following changes are in order:lsm_str
struct publicly available, as to allow allocating them on the stacklsm_str
to any C function that takes a C string is currently very cumbersome, having to copy the string to a new buffer. Ideally, we could just pass the result oflsm_str_ptr
as a C string.lsm_str_set
function that serves the same purpose aslsm_str_overwrite
, but does not free the previous string's contents; this to allow setting an empty stack-allocated string object for the first timeThese changes will make working with the
lsm_str
library much nicer.