Skip to content

perf: memory efficiency and performance #29

Merged
AmirSa12 merged 1 commit intomainfrom
fix/noop-func
Aug 9, 2025
Merged

perf: memory efficiency and performance #29
AmirSa12 merged 1 commit intomainfrom
fix/noop-func

Conversation

@AmirSa12
Copy link
Copy Markdown
Member

@AmirSa12 AmirSa12 commented Aug 9, 2025

No description provided.

@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented Aug 9, 2025

⚠️ No Changeset found

Latest commit: 82e6dbe

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@pkg-pr-new
Copy link
Copy Markdown

pkg-pr-new Bot commented Aug 9, 2025

Open in StackBlitz

npm i https://pkg.pr.new/bombshell-dev/tab/@bombsh/tab@29

commit: 82e6dbe

@AmirSa12 AmirSa12 merged commit 80e3d05 into main Aug 9, 2025
9 checks passed
@AmirSa12 AmirSa12 deleted the fix/noop-func branch August 9, 2025 05:08
@AmirSa12 AmirSa12 changed the title fix: memory efficiency and performance perf: memory efficiency and performance Aug 9, 2025
export function setupPnpmCompletions(completion: Completion) {
completion.addCommand('add', 'Install a package', [], async () => []);
completion.addCommand('remove', 'Remove a package', [], async () => []);
completion.addCommand('add', 'Install a package', [], noopCompletion);
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

i thought descriptions were being retrieved from the package managers themselves as we talked. we should not do that manually.

// TODO: i do not see any completion functionality in this file. nothing is being provided for the defined commands of these package managers. this is a blocker for release. every each of them should be handled.
import { Completion } from '../src/index.js';

const noopCompletion = async () => [];
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

this is not an efficiency and performance win, it's more like a syntactic optimization.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

@Aslemammad, I mean, if we think technically (though it’s a very small difference), the inlined way creates more memory allocations, and more allocations technically mean slightly less efficient memory usage.
but yeah we won’t see a real performance or memory impact either way in this case!

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