Skip to content

refactor[types]: remove unused _NodeMetadataJournal - #5221

Merged
Sporarum merged 4 commits into
vyperlang:masterfrom
Sporarum:remove-metadata-journal
Sep 10, 2026
Merged

Sporarum merged 4 commits into
vyperlang:masterfrom
Sporarum:remove-metadata-journal

Conversation

@Sporarum

Copy link
Copy Markdown
Collaborator

What I did

_NodeMetadataJournal was unused since ddfce52 (from that commit message):

we also no longer need to use the typechecker speculation
machinery for inferring the type of the loop variable. however, the
NodeMetadata code is not removed because it might come in handy at a
later date.

It is now more than 2 years later, and it hasn't been used since.
(and this commit can always be reverted if that need comes)

How I did it

Remove _NodeMetadataJournal, NodeMetadata (became a no-op dict wrapper), and associated tests.

How to verify it

pytest

Commit message

_NodeMetadataJournal was unused since ddfce5273 (from that commit
message): "we also no longer need to use the typechecker speculation
machinery for inferring the type of the loop variable. however, the
NodeMetadata code is not removed because it might come in handy at a
later date."

this commit removes it, `NodeMetadata` (became a no-op dict wrapper),
and the associated test file.

Description for the changelog

(refactor, no user-visible change)

Cute Animal Picture

Put a link to a cute animal picture inside the parenthesis-->

@github-actions

Copy link
Copy Markdown

Gas Changes

No changes detected.

Summary

  • Total tests measured: 560
  • Changed: 0
  • Regressions (gas up): 0
  • Improvements (gas down): 0
  • New tests: 0
  • Deleted tests: 0
  • Newly failing: 0
  • Newly passing: 0

@github-actions

github-actions Bot commented Aug 24, 2026 •

Copy link
Copy Markdown

📊 Bytecode Size Changes (venom)

No changes detected.

Full bytecode sizes

Contract legacy-O2 legacy-Os -O2 -O3 -Os
curvefi/legacy/CurveStableSwapMetaNG.vy 24952 23578 19769 19059 18523
curvefi/amm/stableswap/meta_implementation/meta_implementation_v_700.vy 23610 22805 19565 18627 18314
curvefi/amm/stableswap/implementation/implementation_v_700.vy 24962 23769 19188 18363 18019
curvefi/legacy/CurveStableSwapNG.vy 24473 23298 18749 17981 17636
curvefi/amm/tricryptoswap/implementation/implementation_v_200.vy 20724 19959 17250 16689 16325
curvefi/amm/twocryptoswap/implementation/implementation_v_210.vy 17634 16894 14958 14376 14027
yearnfi/VaultV3.vy 19972 19063 14739 13818 13269
curvefi/legacy/CurveCryptoSwap2.vy 18947 18382 14619 14129 13954
yearnfi/VaultV2.vy 16676 15763 13258 12466 12049
curvefi/amm/stableswap/factory/factory_v_100.vy 14558 13978 11852 10780 10880
curvefi/gauge/child_gauge/implementation/implementation_v_110.vy 12338 11561 9781 9184 8795
curvefi/amm/stableswap/views/views_v_120.vy 12784 12368 9705 9059 9294
curvefi/gauge/child_gauge/implementation/implementation_v_100.vy 12017 11249 9514 8924 8538
curvefi/amm/tricryptoswap/math/math_v_200.vy 11189 11126 9029 8144 8170
curvefi/legacy/CurveCryptoMathOptimized3.vy 11188 11125 9028 8144 8170
curvefi/gauge/child_gauge/implementation/implementation_v_020.vy 10665 9947 8626 8100 7714
curvefi/registries/metaregistry/metaregistry_v_110.vy 7590 6732 6491 5710 5603
curvefi/helpers/router/router_v_110.vy 6717 6717 6251 5733 6035
curvefi/amm/tricryptoswap/views/views_v_200.vy 7821 7776 6111 5896 6045
curvefi/helpers/stable_swap_meta_zap/stable_swap_meta_zap_v_100.vy 7302 7067 5877 5350 5610
curvefi/amm/twocryptoswap/views/views_v_200.vy 6991 6946 5680 5479 5614
curvefi/registries/metaregistry/registry_handlers/stableswap/handler_v_110.vy 6633 6259 5533 4695 5238
curvefi/amm/twocryptoswap/math/math_v_210.vy 6800 6800 5506 5012 5039
curvefi/amm/twocryptoswap/factory/factory_v_200.vy 5540 5252 4617 3917 4047
curvefi/amm/tricryptoswap/factory/factory_v_200.vy 5246 5021 4483 3890 4020
curvefi/gauge/child_gauge/factory/factory_v_201.vy 4844 4547 3901 3675 3511
curvefi/registries/metaregistry/registry_handlers/tricryptoswap/handler_v_110.vy 4241 3939 3718 3334 3429
curvefi/registries/metaregistry/registry_handlers/twocryptoswap/handler_v_110.vy 4186 3884 3671 3251 3329
curvefi/gauge/child_gauge/factory/factory_v_100.vy 4183 3914 3408 3144 2971
yearnfi/VaultFactory.vy 3765 3617 2936 2158 2461
curvefi/registries/address_provider/address_provider_v_201.vy 2973 2782 2613 2440 2353
curvefi/helpers/rate_provider/rate_provider_v_101.vy 3260 3260 2535 2263 2296
curvefi/amm/stableswap/math/math_v_100.vy 3067 3046 2458 2253 2310
curvefi/helpers/rate_provider/rate_provider_v_100.vy 2847 2841 2273 1954 1974
curvefi/helpers/deposit_and_stake_zap/deposit_and_stake_zap_v_100.vy 2322 2316 1782 1611 1670
curvefi/governance/relayer/taiko/relayer_v_001.vy 2068 2064 1731 1510 1558
curvefi/governance/relayer/polygon_cdk/relayer_v_101.vy 1556 1523 1530 1324 1347
curvefi/governance/relayer/arb_orbit/relayer_v_101.vy 1266 1262 1242 1066 1115
curvefi/governance/relayer/op_stack/relayer_v_101.vy 1186 1182 1183 1014 1056
curvefi/governance/relayer/not_rollup/relayer_v_100.vy 1168 1153 1174 1011 1037
curvefi/governance/vault/vault_v_100.vy 964 941 862 823 839
curvefi/governance/relayer/relayer_v_100.vy 496 496 593 490 503
curvefi/governance/agent/agent_v_100.vy 541 541 430 402 406
curvefi/governance/agent/agent_v_101.vy 541 541 430 402 406

@charles-cooper charles-cooper left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hang on, it is used though? like we are using NodeMetadata. the journal functionality is unused, but that doesn't really bother me..

@Sporarum

Copy link
Copy Markdown
Collaborator Author

@charles-cooper
As you prefer, I don't see a value in the journal functionality.
I think it's usually better to avoid mutations, rather than recording them to undo them

There is also be a performance impact to having that journal around, but I have not tested to see if it is significant
(and I have no intuition for whether it would be)

Feel free to close as you see fit

@charles-cooper

Copy link
Copy Markdown
Member

@charles-cooper As you prefer, I don't see a value in the journal functionality. I think it's usually better to avoid mutations, rather than recording them to undo them

There is also be a performance impact to having that journal around, but I have not tested to see if it is significant (and I have no intuition for whether it would be)

Feel free to close as you see fit

oh yea, i'm not concerned about the performance impact. and yes we do not need the journal anymore.. we could keep NodeMetadata as a class but delete the journal part

@Sporarum

Copy link
Copy Markdown
Collaborator Author

@charles-cooper
But then what's the point of NodeMetadata ?

@charles-cooper

Copy link
Copy Markdown
Member

@charles-cooper But then what's the point of NodeMetadata ?

type safety / hygiene / better signatures

@charles-cooper

charles-cooper commented Aug 25, 2026 •

Copy link
Copy Markdown
Member

relatedly makes it easier to refactor if we ever want to add or change functionality to the node metadata

@Sporarum

Copy link
Copy Markdown
Collaborator Author

Done: f43f083

But as you can see, I'm not sure this adds much
Since NodeMetadata is essentially untyped

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f43f0839f7

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread vyper/ast/metadata.py Outdated
@@ -1,83 +1,11 @@
import contextlib

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Run formatting after removing the journal

With the journal code removed, this file is no longer formatted the way CI expects: the workflow runs black --check -C --force-exclude=vyper/version.py ./vyper ./tests ./setup.py and isort --check-only --diff ./vyper ./tests ./setup.py, and both checks now report that vyper/ast/metadata.py needs an extra blank line after this import (black also removes the trailing blank line at EOF). Please run the formatter or remove the now-unused import so the lint job stays green.

Useful? React with 👍 / 👎.

@charles-cooper charles-cooper changed the title refactor[lang]: remove unused _NodeMetadataJournal refactor[lang]: remove unused _NodeMetadataJournal Sep 1, 2026
@charles-cooper

Copy link
Copy Markdown
Member

@Sporarum approved, please fix lint and i think we should also add a typechecker scope in pull-request.yaml workflow

@Sporarum

Copy link
Copy Markdown
Collaborator Author

@Sporarum approved, please fix lint

I had forgotten to push it ...

i think we should also add a typechecker scope in pull-request.yaml workflow

I agree !

However, I don't think it applies for this PR, the issue being neither does any others :/

@charles-cooper charles-cooper changed the title refactor[lang]: remove unused _NodeMetadataJournal refactor[types]: remove unused _NodeMetadataJournal Sep 10, 2026
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 10, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-09-10T12:04:47.356059Z cfc02ff New commits
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@Sporarum
Sporarum enabled auto-merge (squash) September 10, 2026 12:13
@Sporarum
Sporarum merged commit f839ac5 into vyperlang:master Sep 10, 2026
172 checks passed
@Sporarum
Sporarum deleted the remove-metadata-journal branch September 11, 2026 07:12
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.

2 participants