smallnest

package main
import (
    "os"
    "exec"
)

func pipe_commands(commands ...*exec.Cmd) ([]byte, os.Error) {
    for i, command := range commands[:len(commands) - 1] {
        out, err := command.StdoutPipe()
        if err != nil {

smallnest

package main

import (
	"bytes"
	"fmt"
	"io/ioutil"
	"log"

	"golang.org/x/crypto/ssh"
	kh "golang.org/x/crypto/ssh/knownhosts"

smallnest

package main

import (
	"bufio"
	"io/ioutil"
	"os/signal"
	//"syscall"
	"fmt"
	"log"
	"os"

smallnest

package main

import (
	"bufio"
	"io/ioutil"
	"os/signal"
	//"syscall"
	"fmt"
	"log"
	"os"

smallnest

package main

import (
	"flag"
	"fmt"
	"log"
	"os"
	"runtime/pprof"
	"strconv"
	"sync"

smallnest

package main

/*
#include <unistd.h>
*/
import "C"
import (
    "fmt"
    "time"
)

smallnest

package main

import (
	"os"
	"os/exec"
)

func Start(args ...string) (p *os.Process, err error) {
	if args[0], err = exec.LookPath(args[0]); err == nil {
		var procAttr os.ProcAttr

smallnest

package main

import (
	"flag"
	"fmt"
	"log"
	"os"
	"os/signal"
	"syscall"
)

smallnest

/*
	How to simulate classes and virtual methods in Go.
*/

package main

import . "fmt"

type A struct {
	// Set My to outermost object (most derived class) after constructing.

smallnest

How does async work in async-std?

(Phaiax - 2019/12/1 - CC_BY_SA 4.0)

Lately I was porting a software from tokio/futures-1.0 to async-await. I somehow thought async-std was the successor of tokio and ported everything to async-std. 80% in, I noticed that my hyper dependency requires tokio and that it's not possible to replace tokio with async-std without also replacing hyper. Also, tokio and async-std try to solve the same problem. So I started a journey into the inners of the rust async story to find out if it is possible to use both tokio and async-std at the same time. (tl;dr: it is). I had heard of reactors and executors before, but there was much new stuff to discover.