wezm/wezm.net
1
0
Fork 1
mirror of https://github.com/wezm/wezm.net.git synced 2024-12-18 18:29:54 +00:00
Code Issues Projects Releases Packages Wiki Activity

Fix things identified by Di

Browse source
This commit is contained in:
Wesley Moore 2019-03-24 17:30:42 +11:00
parent 2b672eece1
commit 04ba9f0c79
No known key found for this signature in database
GPG key ID: BF67766C0BC2D0EE
2 changed files with 11 additions and 10 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

19
content/technical/2019/03/first-3-weeks-of-professional-rust.md
View file

@ -1,5 +1,5 @@
For the last 15 years as professional programmer I have worked mostly with For the last 15 years as a professional programmer I have worked mostly with
dynamic languages. First [Perl], then [Python], and for the last 10 years or so dynamic languages. First [Perl], then [Python], and for the last 10 years or so,
[Ruby]. I've also been writing [Rust] on the side for personal projects for [Ruby]. I've also been writing [Rust] on the side for personal projects for
nearly four years. Recently I started a new job and for the first time I'm nearly four years. Recently I started a new job and for the first time I'm
writing Rust professionally. Rust represents quite a shift in language writing Rust professionally. Rust represents quite a shift in language
@ -16,7 +16,7 @@ Rust][lifetimes]. I was reasonably confident with them conceptually and their
simple application but our code has some interesting type driven zero-copy simple application but our code has some interesting type driven zero-copy
parsing code that tested my knowledge. When encountering some compiler errors I parsing code that tested my knowledge. When encountering some compiler errors I
was fortunate to have experienced colleagues to ask for help. It's been nice to was fortunate to have experienced colleagues to ask for help. It's been nice to
be extending my knowledge and learning as I go. extend my knowledge and learn as I go.
Interestingly I had mostly been building things without advanced lifetime Interestingly I had mostly been building things without advanced lifetime
knowledge up until this point. I think that sometimes the community puts too knowledge up until this point. I think that sometimes the community puts too
@ -29,7 +29,7 @@ trying to build.
In my second week I implemented a change to make a certain pattern more In my second week I implemented a change to make a certain pattern more
ergonomic. It was refreshing to be able to build the initial functionality and ergonomic. It was refreshing to be able to build the initial functionality and
then make a project wide change, confident that given it compiled after the then make a project-wide change, confident that given it compiled after the
change I _probably_ hadn't broken anything. I don't think I would have had the change I _probably_ hadn't broken anything. I don't think I would have had the
confidence to make such a change as early on in the Ruby projects I've worked confidence to make such a change as early on in the Ruby projects I've worked
on previously. on previously.
@ -42,9 +42,10 @@ language do eliminate whole classes of bugs that you'd need to test for in a
dynamic language but that doesn't mean tests aren't needed. dynamic language but that doesn't mean tests aren't needed.
Rust has great built in support for testing and I've enjoyed being able to Rust has great built in support for testing and I've enjoyed being able to
write tests focussed solely on the behaviour and logic of my code. Instead of write tests focussed solely on the behaviour and logic of my code. Compared to
behaviour and logic in addition to ensuring there are no syntax errors, or that Ruby where I have to write tests that ensure there are no syntax errors, `nil`
`nil` is handled safely, etc. is handled safely, arguments are correct, in addition to the behaviour and
logic.
## Editor and Tooling ## Editor and Tooling
@ -69,7 +70,7 @@ could just click the paths in the error messages.
It's perhaps the combination of working on a foreign codebase and also trying It's perhaps the combination of working on a foreign codebase and also trying
to maximise efficiency when working with others that pushed me to seek out to maximise efficiency when working with others that pushed me to seek out
better tooling for work use. There is a ongoing to work to improve the RLS so I better tooling for work use. There is ongoing to work to improve the RLS so I
may still come back to Neovim and I continue to use it for personal may still come back to Neovim and I continue to use it for personal
projects. projects.
@ -94,7 +95,7 @@ is harder with Rust. `println!` or `dbg!` based debugging can get you a
surprisingly long way and had served me well for most of my personal projects. surprisingly long way and had served me well for most of my personal projects.
When building some parsing code I quickly felt the need to use a real When building some parsing code I quickly felt the need to use a real
debugger in order to step through, and examine execution of a failing test. debugger in order to step through and examine execution of a failing test.
It's possible to do this on the command line with the `rust-gdb` or `rust-lldb` It's possible to do this on the command line with the `rust-gdb` or `rust-lldb`
wrappers that come with Rust. However, I find them fiddly to use wrappers that come with Rust. However, I find them fiddly to use
and verbose to operate. and verbose to operate.

2
content/technical/2019/03/first-3-weeks-of-professional-rust.yaml
View file

@ -4,7 +4,7 @@ extra: Reflecting on the first 3 weeks of writing Rust in my new job.
kind: article kind: article
section: technical section: technical
created_at: 2019-03-24 09:45:00.000000000 +11:00 created_at: 2019-03-24 09:45:00.000000000 +11:00
#updated_at: 2019-03-23T13:16:07+11:00 updated_at: 2019-03-24T17:28:56+11:00
keywords: keywords:
- rust - rust
short_url: short_url: