Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Is there a specific reason to not allow invariant(cond, message, ...args) ? #42

Open
Sceat opened this issue May 8, 2020 · 1 comment
Open

Is there a specific reason to not allow invariant(cond, message, ...args) ? #42

Sceat opened this issue May 8, 2020 · 1 comment

Comments

@Sceat
Copy link

Sceat commented May 8, 2020

invariant is using a defined number of arguments (a,b,c,d,e,f)
imo it should be

invariant(cond, message, ...args) {
	const parsed = message.replace('%s', () => args.shift() || '')
}
@Sceat
Copy link
Author

Sceat commented May 8, 2020

actually #33

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Sceat