Salvador Guzman sguzman

This help only covers the parts of GLSL ES that are relevant for Shadertoy. For the complete specification please have a look at GLSL ES specification

Language:

Version: WebGL 2.0
Arithmetic: ( ) + - ! * / %
Logical/Relatonal: ~ < > <= >= == != && ||
Bit Operators: & ^ | << >>
Comments: // /* */
Types: void bool int uint float vec2 vec3 vec4 bvec2 bvec3 bvec4 ivec2 ivec3 ivec4 uvec2 uvec3 uvec4 mat2 mat3 mat4 mat?x? sampler2D, sampler3D samplerCube
Format: float a = 1.0; int b = 1; uint i = 1U; int i = 0x1;

org-mode syntax - superscripts and subscripts example 1

Add #+OPTIONS: ^:{} to your org-mode file to explicitly enable superscripts and subscripts.

superscripts: To create a superscript put ^{ characters at the start of the superscript text and } at the end of the superscript text, e.g. word^{superscript} will render as word^superscript.
subscripts: To create a subscript put _{ characters at the start of the subscript text and } at the end of the subscript text, e.g. word_{subscript} will render as word_subscript.

References

The RSS Endpoint List

Please refer to this blogpost to get an overview.

Replace *-INSTANCE with one of the public instances listed in the scrapers section. Replace CAPITALIZED words with their corresponding identifiers on the website.

Social Media

Twitter

I've been deceiving you all. I had you believe that Svelte was a UI framework — unlike React and Vue etc, because it shifts work out of the client and into the compiler, but a framework nonetheless.

But that's not exactly accurate. In my defense, I didn't realise it myself until very recently. But with Svelte 3 around the corner, it's time to come clean about what Svelte really is.

Svelte is a language.

Specifically, Svelte is an attempt to answer a question that many people have asked, and a few have answered: what would it look like if we had a language for describing reactive user interfaces?

A few projects that have answered this question:

I think I’ve figured out most parts of the cubical type theory papers; I’m going to take a shot to explain it informally in the format of Q&As. I prefer using syntax or terminologies that fit better rather than the more standard ones.

Q: What is cubical type theory?

A: It’s a type theory giving homotopy type theory its computational meaning.

Q: What is homotopy type theory then?

A: It’s traditional type theory (which refers to Martin-Löf type theory in this Q&A) augmented with higher inductive types and the univalence axiom.

	use std::collections::HashMap;
	use std::fmt;
	use std::io;
	use std::num::ParseFloatError;
	use std::rc::Rc;

	/*
	Types
	*/

	use std::collections::HashMap;
	use std::fmt;
	use std::io;
	use std::num::ParseFloatError;

	/*
	Types
	*/

	#[derive(Clone)]

	FROM liuchong/rustup:musl AS base
	RUN mkdir app
	WORKDIR ./app

	COPY ./Cargo.lock ./Cargo.lock
	COPY ./Cargo.toml ./Cargo.toml

	RUN rustup target add x86_64-unknown-linux-musl
	RUN rustup install nightly
	RUN cargo install cargo-build-deps --verbose --color always

	# Set the control character to Ctrl+Spacebar (instead of Ctrl+B)
	set -g prefix C-space
	unbind-key C-b
	bind-key C-space send-prefix

	# Set new panes to open in current directory
	bind c new-window -c "#{pane_current_path}"
	bind '"' split-window -c "#{pane_current_path}"
	bind % split-window -h -c "#{pane_current_path}"

	# source:http://geocities.com/SiliconValley/heights/7052/opcode.txt
	From: [email protected] (Mark Hopkins)
	Newsgroups: alt.lang.asm
	Subject: A Summary of the 80486 Opcodes and Instructions

	(1) The 80x86 is an Octal Machine
	This is a follow-up and revision of an article posted in alt.lang.asm on
	7-5-92 concerning the 80x86 instruction encoding.

	The only proper way to understand 80x86 coding is to realize that ALL 80x86