cdiggins

using System;
using System.Diagnostics;
using Vim.Logger;

namespace Vim.DotNetUtilities
{
    /// <summary>
    /// This interface is different from the IProgress&lt;T&gt; class in the system library
    /// https://docs.microsoft.com/en-us/dotnet/api/system.iprogress-1?view=netframework-4.8
    /// It was designed to simplify the use case of percentage reporting where the number of steps 

cdiggins

public static byte[] NaivePack(IList<byte[]> buffers)
{
    using (var stream = new MemoryStream())
    using (var bw = new BinaryWriter(stream))
    {
        bw.Write(buffers.Count);
        foreach (var b in buffers)
        {
            bw.Write(b.Length);
            bw.Write(b);

cdiggins

"use strict";

function EvalArithmetic(exprNode)
{
    switch (exprNode.rule.name) 
    {   
        case "expr":
        {
            return EvalArithmetic(exprNode.children[0]);
        }

cdiggins

"use strict";

// Defines a grammar for basic arithmetic 
function CreateArithmeticGrammar(myna)  
{
    // Setup a shorthand for the Myna parsing library object
    let m = myna;    

    // Construct a grammar 
    let g = new function() 

cdiggins

React Best practices

I have summarized and compiled a list of React.JS best practices from various sources across the internet.

From the React docs

• https://reactjs.org/docs/components-and-props.html

  • props must be readonly

• https://reactjs.org/docs/state-and-lifecycle.html