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*.
---
 META6.json | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

(limited to 'META6.json')

diff --git a/META6.json b/META6.json
index 97adef3..df8fa3e 100644
--- a/META6.json
+++ b/META6.json
@@ -10,10 +10,10 @@
   "description": "Module to add deep merge functionality to Hashes",
   "license": "Artistic-2.0",
   "name": "Hash::Merge",
-  "perl": "6",
+  "perl": "6.c",
   "provides": {
     "Hash::Merge": "lib/Hash/Merge.pm6",
-    "Hash::Merge::Unit": "lib/Hash/Merge/Unit.pm6"
+    "Hash::Merge::Augment": "lib/Hash/Merge/Augment.pm6"
   },
   "source-url": "https://github.com/scriptkitties/p6-Hash-Merge.git",
   "tags": [
@@ -23,5 +23,6 @@
   "test-depends": [
     "Test::META"
   ],
+  "api": "1",
   "version": "0.2.0"
 }
-- 
cgit v1.1