Many algorithms in Project Euler do not follow coding styles as mentioned by @dhruvmanila here, or even the standard coding guidelines.

Notes:

• A lot of inconsistencies with the solution functions (a lot of them aren't named as "solution")
• docstring inconsistencies:

>```docstring```
vs
>```
docstring``

GTest exports the following targets:

• GTest::gtest
• GTest::gtest_main
• GTest::gmock
• GTest::gmock_main

This targets should also be available when adding gtest with add_subdirectory (or FetchContent), because this should behave the same way as adding GTest with find_package. So somewhere, we should add the aliases to these targets, i.e.

add_library(GTest::gtest ALIAS 

Describe the solution you'd like to see implemented
When adding channels to a new profile, it has been suggested to know which channels are present in another profile. My suggested solution to this is to have a drop down where the user can select which profile they'd like to display and filters / additions would be based off of that instead of the "All Channels" profile.

**Additional cont

React version:
@types/react@16.9.49
@types/prop-types@15.7.3
ts version 4.0.2

Steps To Reproduce

import React from 'react';
interface A {
    a: number;
}


function foo(param: React.ComponentClass<A>) {
    return param;
}

function foobar<T extends A >(param: React.ComponentClass<T>) {
    foo(param);
}