stacktrace_compat

# Changelog
All notable changes to this project will be documented in this file.

The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/)
and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.html).

## [1.2.2] - 2021-04-02
### Fixed
- test cases that broke on OTP 24.0-rc1

## [1.2.1] - 2020-10-28
### Fixed
- occasional errors upon performing Dialyzer and xref checks concurrently
- Dialyzer-related warnings on recent versions of `rebar3`
- compiler warnings when running tests on OTP versions post- `get_stacktrace()` deprecation

## [1.2.0] - 2020-05-26
### Removed
- compatibility with OTP 18

### Fixed
- test cases that broke under OTP 23
- library version mentioned in documentation example

## [1.1.2] - 2019-11-11
### Changed
- generated documentation as to (tentatively) make it prettier

## [1.1.1] - 2019-06-20
### Fixed
- library version mentioned in documentation example

## [1.1.0] - 2019-06-13
### Removed
- OTP 17 support

## [1.0.2] - 2019-01-19
### Fixed
- unwarranted import of rebar3_hex plugin in library consumers

## [1.0.1] - 2018-07-11
### Fixed
- generation of unsafe stacktrace variables upon the existence of
  multiple try-catch blocks, within a function, with the same hierarchy
  (and equivalent but more contrived cases.)
  E.g, in the following transformed code:
```
function() ->
    try error(foobar)
    catch
        error:foobar:StacktraceCompat444353487_1 ->
            {foobar, StacktraceCompat444353487_1}
    end,

    try error(foobar)
    catch
        error:foobar:StacktraceCompat444353487_1 ->
            % ^^ This unsafe use of 'StacktraceCompat444353487_1'
            % no longer occurs; the generated variable name
            % would now be 'StacktraceCompat444353487_2'.
            {foobar, StacktraceCompat444353487_1}
    end.
```

## [1.0.0] - 2018-06-23
### Added
- ability of replacing most erlang:get_stacktrace() instances with variable captures in OTP 21+