jaredpar

using System;
using System.Reflection.Emit;
using System.Runtime.CompilerServices;
using System.Threading.Tasks;

#nullable disable

// The stand up link https://www.youtube.com/watch?v=jaPk6Nt33KM

// String vs. string

akarpov89

using System.Runtime.CompilerServices;
using static ParsingExtensions;

string input = "Name: Andrew; Age: 31";

string? name = null;
int age = 0;

if (input.TryParse($"Name: {Placeholder(ref name)}; Age: {Placeholder(ref age)}"))
{ 

hyrious

$LazyLoadProfile = [PowerShell]::Create()
[void]$LazyLoadProfile.AddScript(@'
    Import-Module posh-git
'@)
$LazyLoadProfileRunspace = [RunspaceFactory]::CreateRunspace()
$LazyLoadProfile.Runspace = $LazyLoadProfileRunspace
$LazyLoadProfileRunspace.Open()
[void]$LazyLoadProfile.BeginInvoke()

oktupol

#!/bin/bash

# Play Russian Roulette in your terminal. Include this file in your .bashrc with `. roulette.sh`
# Examples:
# sudo roulette rm -rf --no-preserve-root /
# roulette git checkout --orphan tmp && rm -r * && git add -A && git branch -D master && git push --force origin master
# roulette mail -s "Go f*** yourself" "[email protected]" <<< ""
roulette() {
  if [ $(($RANDOM % 6)) -eq 1 ]; then
    $@

shafik

What is the Strict Aliasing Rule and Why do we care?

(OR Type Punning, Undefined Behavior and Alignment, Oh My!)

What is strict aliasing? First we will describe what is aliasing and then we can learn what being strict about it means.

In C and C++ aliasing has to do with what expression types we are allowed to access stored values through. In both C and C++ the standard specifies which expression types are allowed to alias which types. The compiler and optimizer are allowed to assume we follow the aliasing rules strictly, hence the term strict aliasing rule. If we attempt to access a value using a type not allowed it is classified as undefined behavior(UB). Once we have undefined behavior all bets are off, the results of our program are no longer reliable.

Unfortunately with strict aliasing violations, we will often obtain the results we expect, leaving the possibility the a future version of a compiler with a new optimization will break code we th

helmutschneider

import * as ts from 'typescript'
import { Rules, RuleWalker, RuleFailure } from 'tslint'

function find<T>(collection: T[], predicate: (it: T) => boolean): T | null {
    for (const item of collection) {
        if (predicate(item)) {
            return item
        }
    }
    return null