-
UnliftIO increases costs and there is no need to have it in this library - it is better to keep library code in IO monad and have applications that use UnliftIO wrap it.
It would be a breaking chan…
-
```
Too few invocations: Completely synthetic stack trace(s) that point(s) to all
affected interactions
Too many invocations: Truncate after call to matching method, replace name of
proxy class (e.g…
-
This is a great feature request that seems didn't get the excitement of the `i3` people: https://github.com/i3/i3/issues/3738
I'd greatly appreciate if you could add it to sway.
-
```
Too few invocations: Completely synthetic stack trace(s) that point(s) to all
affected interactions
Too many invocations: Truncate after call to matching method, replace name of
proxy class (e.g…
-
```
Too few invocations: Completely synthetic stack trace(s) that point(s) to all
affected interactions
Too many invocations: Truncate after call to matching method, replace name of
proxy class (e.g…
-
```
Too few invocations: Completely synthetic stack trace(s) that point(s) to all
affected interactions
Too many invocations: Truncate after call to matching method, replace name of
proxy class (e.g…
-
the tech stack part, at the bottom of projects cards can be replaced with icons. We can use the tech stack component from vanilla project
-
```
Too few invocations: Completely synthetic stack trace(s) that point(s) to all
affected interactions
Too many invocations: Truncate after call to matching method, replace name of
proxy class (e.g…
-
```
Too few invocations: Completely synthetic stack trace(s) that point(s) to all
affected interactions
Too many invocations: Truncate after call to matching method, replace name of
proxy class (e.g…
-
```
Too few invocations: Completely synthetic stack trace(s) that point(s) to all
affected interactions
Too many invocations: Truncate after call to matching method, replace name of
proxy class (e.g…