Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

memoise Text calls #26

Open
plastikfan opened this issue Aug 27, 2024 · 0 comments
Open

memoise Text calls #26

plastikfan opened this issue Aug 27, 2024 · 0 comments
Assignees
Labels
refactor Refactor code

Comments

@plastikfan
Copy link
Contributor

plastikfan commented Aug 27, 2024

See:

Not all message entries are realistically memoizable. Any messages with dynamic content should not be memoized. Each xxxTemplData entry could have a flag set on them to indicate if it can be memoized. Or we could introduce a new struct that can be composed in which indicates it is memoizable. When Text is called, it will check if it is memoizable and take appropriate action.

tcache?? (Similar to the Linux dcache used to cache inodes to speed up file system performance)

Sync.Map

@plastikfan plastikfan added the refactor Refactor code label Aug 27, 2024
@plastikfan plastikfan self-assigned this Aug 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
refactor Refactor code
Projects
None yet
Development

No branches or pull requests

1 participant