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

Avoid allocation of Writer objects when feasible #2985

Open
slfritchie opened this issue Jul 31, 2019 · 0 comments
Open

Avoid allocation of Writer objects when feasible #2985

slfritchie opened this issue Jul 31, 2019 · 0 comments

Comments

@slfritchie
Copy link
Contributor

In various places, Wallaroo code allocates a new Writer object for a single use when re-use of a long-lived Writer object should be done instead. For example, #2983 (comment) in connector_sink.pony. When feasible, refactor code to use long-lived objects.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant