From 09a8131c63667d9de9ee3921e7f877c09c9092c8 Mon Sep 17 00:00:00 2001
From: Patrick Spek <p.spek@tyil.nl>
Date: Wed, 28 Mar 2018 14:34:24 +0200
Subject: Move Hash::Merge -> Hash::Merge::Augment, new Hash::Merge from
 Hash::Merge::F

Original Hash::Merge is incredibly slow due to the MONKEY. This is
someone that is very unlikely to be what people want. App::Assixt
reports parse time to go from 13s to 7s on first run, 13s to 0.3s on
subsequent runs, which is *massive*.
---
 t/01-thing.t        | 2 +-
 t/02-empty-source.t | 2 +-
 t/03-unit.t         | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

(limited to 't')

diff --git a/t/01-thing.t b/t/01-thing.t
index 4741929..ef674ec 100644
--- a/t/01-thing.t
+++ b/t/01-thing.t
@@ -4,7 +4,7 @@ use v6;
 use lib 'lib';
 use Test;
 
-use Hash::Merge;
+use Hash::Merge::Augment;
 
 my %a;
 my %b;
diff --git a/t/02-empty-source.t b/t/02-empty-source.t
index b404a63..2737d2d 100644
--- a/t/02-empty-source.t
+++ b/t/02-empty-source.t
@@ -6,7 +6,7 @@ use Test;
 
 plan 3;
 
-use Hash::Merge;
+use Hash::Merge::Augment;
 
 my Hash $hash = {
     a => "a",
diff --git a/t/03-unit.t b/t/03-unit.t
index 43d70ff..5230398 100644
--- a/t/03-unit.t
+++ b/t/03-unit.t
@@ -2,7 +2,7 @@
 
 use v6.c;
 
-use Hash::Merge::Unit;
+use Hash::Merge;
 use Test;
 
 plan 2;
-- 
cgit v1.1