Skip to content

perf: Don't pre-allocate memory#172

Open
epage wants to merge 1 commit into
ni:masterfrom
epage:lazy
Open

perf: Don't pre-allocate memory#172
epage wants to merge 1 commit into
ni:masterfrom
epage:lazy

Conversation

@epage

@epage epage commented Aug 3, 2017

Copy link
Copy Markdown
Contributor

No one will probably notice the difference. Oh well.

  • This contribution adheres to CONTRIBUTING.md.
  • New tests have been created for any new features or regression tests for bugfixes.
  • tox successfully runs, including unit tests and style checks (see CONTRIBUTING.md).

No one will probably notice the difference.  Oh well.

Why was this change not applied to ...
- tests: perf doesn't matter, so might as well keep them simple
- examples: keep them simple
@coveralls

coveralls commented Aug 3, 2017

Copy link
Copy Markdown

Coverage Status

Coverage increased (+0.01%) to 64.11% when pulling 017c72c on epage:lazy into f87765f on ni:master.

1 similar comment
@coveralls

coveralls commented Aug 3, 2017

Copy link
Copy Markdown

Coverage Status

Coverage increased (+0.01%) to 64.11% when pulling 017c72c on epage:lazy into f87765f on ni:master.

@coveralls

coveralls commented Aug 3, 2017

Copy link
Copy Markdown

Coverage Status

Coverage increased (+0.01%) to 64.11% when pulling 017c72c on epage:lazy into f87765f on ni:master.

@epage

epage commented Aug 4, 2017

Copy link
Copy Markdown
Contributor Author

I have no clue why mypy is complaining about me using six.moves.

@d-bohls d-bohls self-assigned this Feb 6, 2018
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.

3 participants