Issues • QuackatronHQ/Gigarepo

Consider decorating method with `@staticmethod`

PYL-R0201

Performance

—

3

Consider using `in`

PYL-R1714

Performance

—

3

Unnecessary comprehension

PTC-W0016

Performance

—

2

Avoid empty finalizers

CS-P1000

Performance

—

1

Use `size` instead of `count`

RB-PR1020

Performance

—

1

Use `module` instead of `command`

ANS-E3003

Performance

—

1

Hash merging can be replaced by hash key assignment

RB-PR1017

Performance

—

1

Consider using `.TryGetValue` to access elements in `Dictionary`

CS-P1005

Performance

—

1

Use of compute intensive function in loop condition

PHP-P1000

Performance

—

1

Maps and Sets of URLs can be performance hogs

JAVA-P0057

Performance

—

4

Inefficient use of `String` constructor

JAVA-P0062

Performance

—

1

Use `""` instead of `new String()` to create empty strings

JAVA-P0063

Performance

—

1

`toString` invoked on a string value is useless

JAVA-P0064

Performance

—

1

Explicit invocation of garbage collection is detrimental apart from some benchmarking use cases

JAVA-P0065

Performance

—

1

`Boolean` constructor is inefficient, consider using `Boolean.valueOf` instead

JAVA-P0066

Performance

—

1

`Integer`/`Long` constructor is inefficient, use `valueOf` instead

JAVA-P0067

Performance

—

1

Prefer not to use words image, photo in image alt content

JS-0750

Performance

—

1

Non-interactive elements assigned mouse/keyboard event listeners

JS-0760

Performance

—

2

Found unreachable code

JS-0025

Performance

—

2

Avoid using `setState` in `componentDidMount`

JS-0442

Performance

—

1

Duplicate `polyfills` from `Polyfill.io`

JS-P1002

Performance

—

1

Consider filtering first and then sorting

SC-P1003

Performance

—

1

Consider combining successive `.filter()` calls

SC-P1009

Performance

—

1

Use of inefficient generic algorithm over efficient container based ones

CXX-P2000

Performance

—

1

Inefficient use of `std::vector` in loop

CXX-P2007

Performance

—

1

QuackatronHQ / Gigarepo

Consider decorating method with @staticmethod

Consider using in

Unnecessary comprehension

Avoid empty finalizers

Use size instead of count

Use module instead of command

Hash merging can be replaced by hash key assignment

Consider using .TryGetValue to access elements in Dictionary

Use of compute intensive function in loop condition

Maps and Sets of URLs can be performance hogs

Inefficient use of String constructor

Use "" instead of new String() to create empty strings

toString invoked on a string value is useless

Explicit invocation of garbage collection is detrimental apart from some benchmarking use cases

Boolean constructor is inefficient, consider using Boolean.valueOf instead

Integer/Long constructor is inefficient, use valueOf instead

Prefer not to use words image, photo in image alt content

Non-interactive elements assigned mouse/keyboard event listeners

Found unreachable code

Avoid using setState in componentDidMount

Duplicate polyfills from Polyfill.io

Consider filtering first and then sorting

Consider combining successive .filter() calls

Use of inefficient generic algorithm over efficient container based ones

Inefficient use of std::vector in loop

Consider decorating method with `@staticmethod`

Consider using `in`

Use `size` instead of `count`

Use `module` instead of `command`

Consider using `.TryGetValue` to access elements in `Dictionary`

Inefficient use of `String` constructor

Use `""` instead of `new String()` to create empty strings

`toString` invoked on a string value is useless

`Boolean` constructor is inefficient, consider using `Boolean.valueOf` instead

`Integer`/`Long` constructor is inefficient, use `valueOf` instead

Avoid using `setState` in `componentDidMount`

Duplicate `polyfills` from `Polyfill.io`

Consider combining successive `.filter()` calls

Inefficient use of `std::vector` in loop