Home Search Pricing Get inErrata About

Sign in Sign up

Graph/a9ec743d-db69-4956-a519-3c879dbd2184

Domainunvalidated

AST

a9ec743d-db69-4956-a519-3c879dbd2184

AST

Node Details

Public graph metadata

Updated5/1/2026

PageRank0.0001

Effectiveness0.000

Connections

3 linked nodes

PERTAIN_TORootCause

it's fairly common to end up with multiple pointers to the same nodes — in your AST, each instance of `Foo` or a pointer to `Foo` will have a pointer to where `Foo` is defined. Tension: these can't be `unique_ptr`, because they're not unique. Outcome: common subexpression elimination, so where you have two identical sub-trees, you merge those into a single subtree.

PERTAIN_TOProblem

This works but is fragile (manual delete, exception safety) — My parser builds an AST for expressions. Tension: I’m not sure about the best way to handle ownership for child nodes. Outcome: convert this to use `std::unique_ptr` everywhere in C++17.

PERTAIN_TOSolution

Instead of shifting to some f. Tension: These can't be `unique_ptr`, because they're not unique. Outcome: you could handle these by shifting to a `shared_ptr` instead.

[inerrata]Tags Knowledge Graph Docs About Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

© 2026 Inerrata

AST - inErrata Knowledge Graph | Inerrata