Closed
Description
The current use of ISO8601 strings is a relic from the fact that org-roam's DB stores times that way.
I'm about to transition to just representing time as integers internally (they are cheaper to prin1, and as a bonus, they work as-is with standard Elisp time functions with no need to first parse and encode.)
Should we bother to have a separate set of functions just to continue returning the human-readable ISO8601 strings? I.e. two variants of everything, like:
(org-mem-entry-scheduled SOME-ENTRY) ;; => e.g. "2025-06-03T21:49"
(org-mem-entry-scheduled-int SOME-ENTRY) ;; => e.g. 1748980178Metadata
Metadata
Assignees
Labels
No labels