Skip to content

Conversation

@cratelyn
Copy link
Member

these bounds are extensive, but don't serve a mechanical purpose at the
moment.

we can simplify our route metrics layer in the outbound proxy by
removing them.

Signed-off-by: katelyn martin [email protected]

these bounds are extensive, but don't serve a mechanical purpose at the
moment.

we can simplify our route metrics layer in the outbound proxy by
removing them.

Signed-off-by: katelyn martin <[email protected]>
@cratelyn cratelyn self-assigned this Sep 24, 2025
@cratelyn cratelyn marked this pull request as ready for review September 24, 2025 15:45
@cratelyn cratelyn requested a review from a team as a code owner September 24, 2025 15:45
Copy link
Member

@olix0r olix0r left a comment

Choose a reason for hiding this comment

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

So, these aren't load-bearing, but they are a helpful assertion if changes are made that break the stack's compilation: these assertions will give a clearer indication of why the N type isn't used.

At a minimum, I'd suggest preserving the N: svc::NewService<T> assertion which is idiomatic and lightweight

> So, these aren't load-bearing, but they are a helpful assertion if
> changes are made that break the stack's compilation: these assertions
> will give a clearer indication of why the N type isn't used.
>
> At a minimum, I'd suggest preserving the `N: svc::NewService<T>`
> assertion which is idiomatic and lightweight

this commit restores the innermost bound that `N` is a `NewService<T>`.

Signed-off-by: katelyn martin <[email protected]>
@cratelyn
Copy link
Member Author

cratelyn commented Sep 24, 2025

that's a fair point! i've pushed 0e166d3, which restores the innermost N: NewService<T> bound. this should give us the same benefits, indicating when N is liable to break compilation.

@cratelyn cratelyn requested a review from olix0r September 24, 2025 20:42
@cratelyn cratelyn merged commit d7ea041 into main Sep 26, 2025
15 checks passed
@cratelyn cratelyn deleted the kate/app-outbound.remove-new-service-bounds branch September 26, 2025 14:48
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