* implement Display for ink_lang::Error

* re-export HexLiteral trait from ink_lang_ir crate

* use big-letters for hex-encoded message and constructor identifiers in codegen

* improve panic messages in dispatch codegen for call and deploy fns

* improve macro hygiene in dispatch codegen

* add ir::Selector::into_be_u32 method

* improve and modernize dispatch selector namespace codegen

* Exit with 1 in case of timeout

* Increase timeout to 1h, make configuration easier

* Echo timeout

* check that argument in #[ink(namespace = "argument")] is a Rust identifier

* add UI tests for #[ink(namespace = "..")] ink! property

# Conflicts:
#	crates/lang/macro/tests/compile_tests.rs
#	crates/lang/macro/tests/ui/fail/N-01-namespace-invalid-identifier.rs
#	crates/lang/macro/tests/ui/fail/N-01-namespace-invalid-identifier.stderr
#	crates/lang/macro/tests/ui/fail/N-02-namespace-invalid-type.rs
#	crates/lang/macro/tests/ui/fail/N-02-namespace-invalid-type.stderr
#	crates/lang/macro/tests/ui/fail/N-03-namespace-missing-argument.rs
#	crates/lang/macro/tests/ui/fail/N-03-namespace-missing-argument.stderr

* fix error message for non-identifier namespace argument

* add HexLiteral utility trait to expand hex-encoded integer literals

* add ir::Selector::hex_lits method

* expand into hex-encoded integer literals for metadata selectors

* simplify Selector::hex_lits method using array::map API

* add unit test for Selector::hex_lits method

* miscellaneous improvements to macro hygiene in derive macros

* fix storage_derive UI tests

* make #[ink(selector = ..)] take an integer instead of a string

Also warn about deprecation if a user still uses the old string parameter.

* update tests for new selector int parameter

* update contract examples for new selector int parameter

* remove unused regex dependency from ink_lang_ir

Also remove unnecessary regex dependency from ink_lang_codegen

* update README for new selector int parameter

Also update namespace parameter description.

* update preliminary release notes

* update spellcheck dict

* Derive `Default`

* Fix `field is never read`

* Fix `clippy::derivable_impls`

* Fix `dead_code`

The `struct` is only a public-facing API.

* Get rid of `allow(dead_code)`

* Revert "Get rid of `allow(dead_code)`"

This reverts commit 6b9a95f9.

* Revert "Fix `dead_code`"

This reverts commit 42ab18be.

* New approach to fix `dead_code`

* Fix naming

* Reflect that `return_type` never needs to be read

* Fix typo

* CI: chore

* CI: fix codecov job

* CI: remove `-Clink-dead-code `

* CI: chore

* Update release notes

* Set version for `cargo-contract`

This change fixes links pointing to wrong lines of example codes on README. I updated these links to specify the same lines as originally intended.

At the time the links were specified, they intended to link these lines:
https://github.com/paritytech/ink/blob/c85cb7822c227f4b186e19225630846553cf28da/examples/trait-erc20/lib.rs#L49-L51
https://github.com/paritytech/ink/blob/c85cb7822c227f4b186e19225630846553cf28da/examples/erc20/lib.rs#L278-L280

* Bump version to rc5

* Add release notes

The function was recently marked as safe:
https://doc.rust-lang.org/nightly/core/arch/wasm32/fn.unreachable.html.

>This function is safe to call and immediately aborts the execution.

Follow-up to https://github.com/paritytech/substrate/pull/9550.

* Adjust error fixtures to nightly changes

* Update fixtures for `nightly-2021-08-13`

* Change pipeline to use vault secrets

Add more vault CI variables

Add more vault CI variables

Add comment line

Pass Vault url var to downstream job

Pass Vault path and role vars to downstream job

Comment out vault-secrets from ink-waterfall

Test vault-secrets on another job

Revert last change

Hardcoded Vault variables

Remove hardcoded vars

Try to get vault vars from another stage

Populate secrets directly in the job

Move Vault access variables to the top

Add secrets to non related jobs for test

Add secrets to non related jobs for test purpose

From secrets from non related jobs

Fix typo

Move vault vars to anchor

Move anchor call after job vars

* Move vault access vars to the top

* Remove `DispatchRetCode`

* Replace unwrap with expect

* Unlicense examples

* Remove license header from examples

* Disable license header check for examples

* Import quickcheck macro only for bump allocator

The fuzz tests exist only in the bump allocator.

* Apply `cargo fmt`

* Add clippy flag `--all-targets`

* Fix `redundant_closure`

* Fix `redundant_clone`

* Fix `clone_on_copy`

* Fix `needless_borrow`

* Fix `bool_assert_comparison`

* Fix `len_zero`

* Fix `stable_sort_primitive`

* Forward feature

* Allow `type_complexity`

* Fix `unnecessary_mut_passed`

* Fix `manual_map`

* Fix `match_like_matches_macro`

* Remove duplicate test

* Fix `new_without_default`

* Fix `match_ref_pats`

* Allow clippy rules for  tests

* Fix `unit_arg`

* Apply `cargo fmt`

* Add explanatory comments

* Remove `--all-targets` for Wasm tests

* Fix `or_fun_call`

* Fix `bool_comparison`

* Fix `needless_collect`

* Revert "Forward feature"

This reverts commit 472c50ed.

* Fix `bool_assert_comparison`

* Deactivate test because of feature issue with dev-dependencies

* Add flag

* Fix `unique_topics` tests

* Allow `clippy:bool_assert_comparison`

* Revert "Fix `bool_assert_comparison`"

This reverts commit bceb2dc2.

* Revert "Fix `bool_comparison`"

This reverts commit 02960f98.

* Fix flags positioning

* Add comment for clarification

* Fix comparison

* Do not check all targets for target = wasm32

* Adapt `check-workspace.sh` with clippy flag

* Add clarification comment

* Ignore test

* Revert `CLIPPY_FLAGS` hack

* Link ink! issue

* Fix `assert`'s

* Fix `assert`'s

* Improve language

* Add test with mocked chain extension

* Export off-chain trait `ChainExtension`

* Add missing space

* Remove unequal assert

* Force the `DEBUG_ENABLED = enabled` code to be executed when RPC is used

* Fix clippy

* Flip the conditional

* Utilize `--recursive` instead of loop

* Increase verbosity level

* Add missing words to dictionary

* Add `Fixed` entry for #842

* Replace `3.0.0-rc3` with `3.0.0-rc4`

* Add bump allocator to release notes

* Add fuzz tests for `StorageVec::binary_search*`

* Decrease number of fuzz tests which are run

We found that bugs are usually already found
with low numbers.

* Apply suggestions from code review

Co-authored-by: Hernando Castano <HCastano@users.noreply.github.com>

* Improve expect

* Fix variable naming

Co-authored-by: Hernando Castano <HCastano@users.noreply.github.com>

* Add bump allocator skeleton

* Implement `alloc` for our bump allocator

* Make the allocator usable globally

* Remove unused `init()` function

* Nightly RustFmt

* Use global mutable static instead of Mutex

This will reduce our use of dependencies which will hopefully
reduce our final Wasm binary size.

Also, apparently spinlocks aren't actually all that efficient.
See: https://matklad.github.io/2020/01/02/spinlocks-considered-harmful.html

* Stop assuming that memory is allocated at address `0`

* Remove semicolon

* Use correct address when checking if we're OOM

* Remove unnecessary unsafe block

* Return null pointers instead of panicking

Panicking in the global allocator is considered undefined behaviour.

* Use `checked_add` when getting upper limit memory address

* Use `MAX` associated const instead of `max_value`

* Inline `GlobalAlloc` methods

* Turns out I can't early return from `unwrap_or_else` 🤦

* Rollback my build script hacks

* Add initialization function to allocator

* Add some docs

* Make the bump allocator the default allocator

* Allow bump allocator to be tested on Unix platforms

* Remove unecessary checked_add

* Add error messages to unrecoverable errors

* Remove `init` function from allocator

Instead we now request a new page whenver we need it, regardless
of whether or not it's the first time we're allocating memory.

* Try switching from `mmap` to `malloc` when in `std` env

* Fix `is_null()` check when requesting memory

* Stop requesting real memory for `std` testing

Instead this tracks pages internally in the same way that the Wasm
environment would. This means we can test our allocator implementation
instead of fighting with `libc`.

* Gate the global bump allocator when not in `std`

* Allow for multi-page allocations

* Update the module documentation

* Override `alloc_zeroed` implementation

* Forgot to update Wasm target function name

* Appease the spellchecker

* Use proper English I guess

* Get rid of `page_requests` field

* Explicitly allow test builds to use test implementation

* All link to zero'd Wasm memory reference

* Check that our initial pointer is 0 in a test

* Add `cfg_if` branch for non-test, `std` enabled builds

* Simplify `cfg_if` statement

error: constructor `lazy` has the same name as the type
	   --> crates/storage/src/lazy/mod.rs:121:5

	       121 | /     pub(crate) fn lazy(key: Key) -> Self {
	       122 | |         Self {
	       123 | |             cell: LazyCell::lazy(key),
	       124 | |         }
	       125 | |     }
		   | |_____^

	= note: `-D clippy::self-named-constructor` implied by `-D warnings`
	= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#self_named_constructor

* Revert me: Remove `codecov` CI check

* Print `cargo-spellcheck` version