Skip to content

Conversation

@H1ghBre4k3r
Copy link

This PR aims to refactor some parts of the example code.

E.g., it introduces the usage of the Partial<T> type, takes usage of restructuring and reduces code duplication.

/** Subtracts two 2D vectors. */
export function sub(lhs: PartialVec2, rhs: PartialVec2): Vec2 {
return { x: (lhs.x ?? 0) - (rhs.x ?? 0), y: (lhs.y ?? 0) - (rhs.y ?? 0) };
return add(lhs, scale(rhs, -1));
Copy link
Owner

Choose a reason for hiding this comment

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

Yeah we could do this, my idea was that subtraction is so fundamental that it ought to be as fast as possible, so I'd actually lean towards keeping it as is (though perhaps we'd want to default the parameters to { x = 0, y = 0 } to make it less verbose).

/** Scales a 2D vector. */
export function scale(lhs: PartialVec2, rhs: number): Vec2 {
return { x: (lhs.x ?? 0) * rhs, y: (lhs.y ?? 0) * rhs };
export function scale({ x = 0, y = 0 }: PartialVec2, rhs: number): Vec2 {
Copy link
Owner

Choose a reason for hiding this comment

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

If we default these parameters, the vector no longer needs to be a PartialVec2, right?

Suggested change
export function scale({ x = 0, y = 0 }: PartialVec2, rhs: number): Vec2 {
export function scale({ x = 0, y = 0 }: Vec2, rhs: number): Vec2 {

Also it would be great if we could use this trick for add and sub too, for consistency.

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