a-b-street / a-b-street/severance_snape

Rethink how severance / WithTraffic connections are handled

Open
#30 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Svelte
Stars
8
Forks
1
PR merge metrics
No merged PRs in 30d

Description

The preprocessing is brute force. It might mess up the "cross anywhere" strategy. The current approach has some TODOs to be careful with.

It might be worth explicitly modeling all or some turns upstream in `graph`, but at what perf cost?

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue mentions preprocessing in the graph and a 'cross anywhere' strategy. Look at the code around severance and WithTraffic connections, likely in the graph module. Understand the current brute-force approach and the TODOs. Evaluate performance implications of modeling turns upstream. Start by finding where connections are handled and the existing TODOs.

Written by the indexing model from the issue text.

Assessment

Domain
backend-api-design
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.