DEV Community: Debugg

Debugging story of the week: Cargo refused to build my project - A Rust debugging story!

Syed Faraaz Ahmad — Sat, 29 Feb 2020 08:38:35 +0000

This is Debugging Story of the Week. A series where each week I post my favourite Debugging story from the interwebs, and why I think they're interesting. You are most definitely invited to share your debugging story.

This week it is from Raunak (@rrampage), it's my favourite because it shows how your code can fail to compile even when you've done nothing wrong. You can install the language using the right tools, write the perfect code, use all secure packages that are compatible with each other, and yet your code can fail to compile. His knowledge of compilers and linkers came in handy while debugging and thankfully the Cargo Book had good documentation. If a tool doesn't have proper documentation, it is easy to get lost in guessing where the error could be originating from.

Check out Raunak's story below and tell me what you think.

https://dev.to/rrampage/cargo-refused-to-build-my-project---a-rust-debugging-story-25e9

We all have debugging stories where in the end, we might even feel stupid (we all do). I think we should all share these stories with each other, so that when someone comes across a similar problem, they don't have to spend time pulling their hairs out wondering what went wrong.

So, what's your debugging story?

The "best" web framework?

Syed Faraaz Ahmad — Wed, 26 Feb 2020 19:36:48 +0000

What is the best web framework to learn?

This is a common question among people just starting out in the field of web development. As a beginner, it is easy to assume that there is probably one major framework that everyone uses. Learning this framework would be enough to quickly land you a job, right?

In my opinion, there is no "best" web framework. Only one that is best for the given requirements and constraints.

What do you think?

Building a web server in Golang

Syed Faraaz Ahmad — Mon, 10 Feb 2020 14:54:33 +0000

This post is a solution to the "Adam doesn't know routing" problem on Debugg. Visit Debugg at https://debugg.me

What we need here is a simple web server and one route, the / or "root" route, let's say.

There's a built-in package called net/http that can help us here. Open the main.go file, and import the package.

// main.go

package main

import "net/http"

func main() {

}

The official documentation of the package shows an example for the function ListenAndServe, which is just what we need.

// main.go

...

func main() {
    http.ListenAndServe(":8080", nil)
}

which will start an http server on port 8080. Now we need to return "Hello, world!" on the root route. For this we use a HandleFunc and pass it the route path and the handler function.

// main.go

...

func helloHandler(w http.ResponseWriter, _ *http.Request) {}

func main() {
    http.HandleFunc("/", helloHandler)
    http.ListenAndServe(":8080", nil)
}

to return "Hello, World!", we invoke io.WriteString by passing in the ResponseWriter instance and "Hello, World!".

The final file looks as follows

package main

import (
    "io"
    "log"
    "net/http"
)

func helloHandler(w http.ResponseWriter, _ *http.Request) {
    io.WriteString(w, "Hello, World!")
}

func main() {
    http.HandleFunc("/", helloHandler)
    log.Fatal(http.ListenAndServe(":8080", nil))
}

Visit Debugg at https://debugg.me