https://github.com/skellock/crappyassert
https://github.com/skellock/crappyassert
Last synced: about 1 year ago
JSON representation
- Host: GitHub
- URL: https://github.com/skellock/crappyassert
- Owner: skellock
- Created: 2019-01-22T16:31:32.000Z (over 7 years ago)
- Default Branch: master
- Last Pushed: 2019-01-22T16:31:38.000Z (over 7 years ago)
- Last Synced: 2025-02-05T03:20:27.589Z (over 1 year ago)
- Language: Nim
- Homepage:
- Size: 1.95 KB
- Stars: 0
- Watchers: 3
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# crappyassert 💩
[](https://circleci.com/gh/skellock/crappyassert)
A [`nim`](https://nim-lang.org) package which wraps `doAssert` so it prints nicer errors.
# What is this nonsense?
I like `doAssert`, but I sure wish it was easier to read.
# Installing
`nimble install https://github.com/skellock/crappyassert`
# Usage
```nim
import crappyassert
true === false # calls `doAssert true == false`
```
# Why Not?
* custom operators suck?
* nobody likes more dependencies?
* you don't use `doAssert`
* you use anything other than `==` when calling `doAssert`
# Changelog
**`0.1.0`** - Jan 22, 2019
- Initial release
# Requirements
- Nim 0.19.2+
# Installing
`nimble install https://github.com/skellock/crappyassert#head`
( NOTE: I haven't submitted this to `nimble` just yet. )
# License
MIT
# Contributing
Fork it. Pull it. Patch it. Push it.
Send a PR, that should do it.