xgalaxy

> 
> 
> You can try this one, it worked for me both from command line and VS
> (msbuild 15.7.177.53362):
> **ProjectReference in csproj:**
> 
> ```
>     <ProjectReference Include="..\MyVcx\My.vcxproj">
>       <Project>{ProjectGuid}</Project>
>       <Name>projectname</Name>

xgalaxy

Memory<T> usage guidelines

This document describes the relationship between Memory<T> and its related classes (MemoryPool<T>, IMemoryOwner<T>, etc.). It also describes best practices when accepting Memory<T> instances in public API surface. Following these guidelines will help developers write clear, bug-free code.

First, a tour of the basic exchange types

• Span<T> is the basic exchange type that represents contiguous buffers. These buffers may be backed by managed memory (such as T[] or System.String). They may also be backed by unmanaged memory (such as via stackalloc or a raw void*). The Span<T> type is not heapable, meaning that it cannot appear as a field in classes, and it cannot be used across yield or await boundaries.

• Memory is a wrapper around an object that can generate a Span. For instance, Memory instances can be backed by T[], System.String (readonly), and even SafeHandle instances. Memory cannot be backed by "transient" unmanaged me

xgalaxy

Memory<T> API documentation and samples

This document describes the APIs of Memory<T>, IMemoryOwner<T>, and MemoryManager<T> and their relationships to each other.

See also the Memory<T> usage guidelines document for background information.

First, a brief summary of the basic types

• Memory<T> is the basic type that represents a contiguous buffer. This type is a struct, which means that developers cannot subclass it and override the implementation. The basic implementation of the type is aware of contigious memory buffers backed by T[] and System.String (in the case of ReadOnlyMemory<char>).

xgalaxy

In this gist I would like to describe an idea for GraphQL subscriptions. It was inspired by conversations about subscriptions in the GraphQL slack channel and different GH issues, like #89 and #411.

Conceptual Model

At the moment GraphQL allows 2 types of queries:

• query
• mutation

Reference implementation also adds the third type: subscription. It does not have any semantics yet, so here I would like to propose one possible semantics interpretation and the reasoning behind it.

xgalaxy

// Simplified scope stack implementation
// http://www.dice.se/wp-content/uploads/2014/12/scopestacks_public.pdf

#include <new>
#include <cstdio>
#include <cassert>

typedef unsigned char u8;

class LinearAllocator {

xgalaxy

#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-
Language                                  : Cpp
BasedOnStyle                              : Google
Standard                                  : Cpp11
#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-
AccessModifierOffset                      : -4
BreakBeforeBraces                         : Stroustrup
ColumnLimit                               : 160
IndentWidth                               : 4
IndentPPDirectives                        : AfterHash

xgalaxy

// From: http://www.codersnotes.com/notes/easy-preprocessor-defines/

#define ON                        +
#define OFF                       -
#define USING(x)                  ((1 x 1) == 2)

// Example usage:
#define BIG_ENDIAN                ON
#if USING(BIG_ENDIAN)
    // do whatever

xgalaxy

using System;
using System.Collections;
using UnityEngine;

public class Testing : MonoBehaviour
{
	void Start()
	{
		// In C#, this is an 'Anonymous Type'
		// A new System.Type is generated for it at compile type