forked from cadey/xesite
first attempt
This commit is contained in:
parent
fa13e57835
commit
2622ccf6cb
|
@ -1,6 +1,7 @@
|
|||
---
|
||||
title: "TL;DR Rust"
|
||||
date: 2020-09-19
|
||||
series: rust-for-gophers
|
||||
tags:
|
||||
- rust
|
||||
- go
|
||||
|
|
|
@ -1,6 +1,7 @@
|
|||
---
|
||||
title: Rust Crates that do What the Go Standard library Does
|
||||
date: 2020-09-27
|
||||
series: rust-for-gophers
|
||||
tags:
|
||||
- rust
|
||||
---
|
||||
|
|
|
@ -0,0 +1,32 @@
|
|||
---
|
||||
title: Time, Regexes and Testing
|
||||
date: 2020-10-04
|
||||
series: rust-for-gophers
|
||||
tags:
|
||||
- rust
|
||||
---
|
||||
|
||||
# Time, Regexes and Testing
|
||||
|
||||
Previously on [Rust for Gophers](/blog/series/rust-for-gophers) (name is a work
|
||||
in progress, ideas would be lovely) we covered logging, templating and basic
|
||||
HTTP client/server operations. Go's standard library also has support from some
|
||||
other things too, such as time handling, regular expressions and unit testing.
|
||||
Today we are going to cover their analogs in Rust.
|
||||
|
||||
## Testing
|
||||
|
||||
Programs have a tendency to not do what you want when you write them. Sometimes
|
||||
it's worth trying to see what code actually does and make sure it's what you
|
||||
want it to do. This can help a lot when you are ensuring that types are
|
||||
converted, the right HTTP responses are returned and that any other effects are
|
||||
what you want.
|
||||
|
||||
[We plan to go into much more detail about this in the future, however this is
|
||||
just enough about how testing in Rust works to help show these
|
||||
examples.](conversation://Mara/hacker)
|
||||
|
||||
## Time
|
||||
|
||||
## Regexes
|
||||
|
Loading…
Reference in New Issue