We have several quite large examples that live in our docs:

1. https://github.com/dry-python/returns/blob/master/docs/pages/future.rst#futureresult
2. Number example from: https://github.com/dry-python/returns/blob/master/docs/pages/contrib/hypothesis_plugins.rst#check_all_laws
3. https://github.com/dry-python/returns/blob/master/docs/pages/context.rst#requirescontextfutureresult-container

https://pypi.org/project/toml-sort/

It would be nice to see aiohttp integration with your library.

When we define a class like this:

def func():
    ...

class MyClass:
    my_func = lambda self, arg: arg

# or
class MyAnotherClass:
    my_func = func

The coverage plugin will consider the my_func as coveraged without any tests.
This behavior is expected because for it the my_func is an attribute!

I think it will be great use the normal signature, this will en

Just like I have this issue on neomatrix369/awesome-ai-ml-dl#54, I have found a way to manually check for deadlinks in all of my markdown files in a repo.

I think there should be something that looks for such links in .rst and other document files as well.

When we find out, it would be good to add it to the pre-commit CI/CD GH action.

Can also be added to t