berkus

/*
 Referenced from:
 http://web.archive.org/web/20120110153227/http://weegen.home.xs4all.nl/eelis/analogliterals.xhtml
*/

#ifndef ANALOGLITERALS_HPP
#define ANALOGLITERALS_HPP

namespace analog_literals {

berkus

#![feature(unboxed_closures, fn_traits)]

fn main() {
    let add = |a: i32, b: i32| a + b;
    let sqr = |a: i32| a.pow(2);
    let add_two = |a: i32| a + 2;

    assert_eq!(chain(add, sqr)(2, 3), 25);
    assert_eq!(
        chain(

berkus

use std::collections::hash_map::Entry;
use std::collections::HashMap;

trait EntryExt<'a, K, V>: 'a {
    fn or_insert_with2<F: FnOnce(&K) -> V>(self, f: F) -> &'a mut V;
}

impl<'a, K, V> EntryExt<'a, K, V> for Entry<'a, K, V> {
    fn or_insert_with2<F: FnOnce(&K) -> V>(self, f: F) -> &'a mut V {
        match self {

berkus

trait Def<T> {
    fn def(&self, foo: T) -> bool;
}

impl<T, Func> Def<T> for Func
  where Func: Fn(T) -> bool
{
    fn def(&self, foo: T) -> bool {
        (self)(foo)

berkus

#![allow(mutable_transmutes)]
use std::mem::transmute;

fn main() {
    let a: Vec<u64> = Vec::new();
    let r = &a;
    let r: &mut Vec<u64> = unsafe { transmute(r) };
    r.push(1488);
    println!("{:?}", a);
    

berkus

Physical layer

The dongle itself is sending out data using 802.11a (5 GHz WiFi) with OFDM and 6 Mbit/s data rate:

Radiotap Header v0, Length 38
    Header revision: 0
    Header pad: 0
    Header length: 38
    Present flags

berkus

WASM Rust to Node Example

Use only > 8.x.x NodeJS version

Install Rust before using this tutorial: curl https://sh.rustup.rs -sSf | sh

Create dirs:

mkdir wasmRustNodeExample

cd wasmRustNodeExample

berkus

trait Trait: AsTrait {
    fn get_answer(&self) -> i32;
}

struct S;

impl Trait for S {
    fn get_answer(&self) -> i32 { 42 }
}

berkus

#![feature(result_map_or_else)]

extern crate serde; // 1.0.84
extern crate serde_derive; // 1.0.84
extern crate serde_json; // 1.0.34

use serde::Serialize;

#[derive(Debug, Serialize)]
#[serde(tag = "status", content = "result")]

berkus

1. Separation of immutable and mutable logic

Quite a lot of different people have been on the same trail of thought. Gary Bernhardt's formulation of a "functional core, imperative shell" seems to be the most voiced.

"Boundaries" - Gary Bernhardt

"Imperative shell" that wraps and uses your "functional core".. The result of this is that the shell has fewer paths, but more dependencies. The core contains no dependencies, but encapsulates the different logic paths. So we’re encapsulating dependencies on one side, and business logic on the other side. Or put another way, the way to figure out the separation is by doing as much as you can without mutation, and then encapsulating the mutation separately. Functional core — Many fast unit tests. Imperative shell — Few integration tests

https://www.youtube.com/watch?v=yTkzNHF6rMs