$/
artifacts/
build/
docs/
lib/
packages/
samples/
src/
tests/
| public class Executor : ReceiveActor | |
| { | |
| readonly Kernel _kernel; | |
| public Executor(Kernel kernel) | |
| { | |
| _kernel = kernel; | |
| Receive<Tuple<Command,ActorRef>[]>(ExecuteCommands); | |
| } | |
| private bool ExecuteCommands(Tuple<Command,ActorRef>[] tuples) |
| namespace Newtonsoft.Json.Converters | |
| open Microsoft.FSharp.Reflection | |
| open Newtonsoft.Json | |
| open System | |
| type IdiomaticDuConverter() = | |
| inherit JsonConverter() | |
| [<Literal>] |
There are certain files created by particular editors, IDEs, operating systems, etc., that do not belong in a repository. But adding system-specific files to the repo's .gitignore is considered a poor practice. This file should only exclude files and directories that are a part of the package that should not be versioned (such as the node_modules directory) as well as files that are generated (and regenerated) as artifacts of a build process.
All other files should be in your own global gitignore file:
- Create a file called
.gitignorein your home directory and add any filepath patterns you want to ignore. - Tell git where your global gitignore file is.
Note: The specific name and path you choose aren't important as long as you configure git to find it, as shown below. You could substitute
.config/git/ignorefor.gitignorein your home directory, if you prefer.
| Num threads: 10 | |
| Start: 2015-08-20 01:42:10 | |
| Reads: 133758452 | |
| Writes: 66050 | |
| Reads/s: 4458615,06666667 | |
| Writes/s: 2201,66666666667 | |
| Total: 133824502 | |
| TPS: 4460816,73333333 | |
| Stop time: 2015-08-20 01:42:50 |
/.git/config
[remote "origin"]
url = ssh://git@git.dev.viaeuropa.int:7999/brikks/brikks.git
fetch = +refs/heads/*:refs/remotes/origin/*
fetch = +refs/pull-requests/*/from:refs/remotes/origin/pull-requests/*
fetch = +refs/pull-requests/*/merge:refs/remotes/origin/pull-requests-merge/*
| {-# LANGUAGE ApplicativeDo #-} | |
| {-# LANGUAGE ConstrainedClassMethods #-} | |
| {-# LANGUAGE ConstraintKinds #-} | |
| {-# LANGUAGE DataKinds #-} | |
| {-# LANGUAGE DeriveFunctor #-} | |
| {-# LANGUAGE DeriveGeneric #-} | |
| {-# LANGUAGE FlexibleContexts #-} | |
| {-# LANGUAGE FlexibleInstances #-} | |
| {-# LANGUAGE IncoherentInstances #-} | |
| {-# LANGUAGE InstanceSigs #-} |
XML processing modules may be not secure against maliciously constructed data. An attacker could abuse XML features to carry out denial of service attacks, access logical files, generate network connections to other machines, or circumvent firewalls.
The penetration tester running XML tests against application will have to determine which XML parser is in use, and then to what kinds of below listed attacks that parser will be vulnerable.
+--------------------+--------------------+-------------------------+--------------------+
|Operation | F#+ / F# |F#+ Haskell Compatibility|Haskell |
+====================+====================+=========================+====================+
|List.append | @ | | ++ |
+--------------------+--------------------+-------------------------+--------------------+
|Function composition| f << g | f . (g) | f . g |
+--------------------+--------------------+-------------------------+--------------------+
| | <| | $ | $ |
+--------------------+--------------------+-------------------------+--------------------+
+----------------------+--------------------+--------------------+--------------------+
| Operation | F-Sharp | Compability | Haskell |
+======================+====================+====================+====================+
| List.append | @ | | ++ |
+----------------------+--------------------+--------------------+--------------------+
| Function composition | f << g | f . (g) | f . g |
+----------------------+--------------------+--------------------+--------------------+
| | = | == | == |
+----------------------+--------------------+--------------------+--------------------+