blob: 87f3fdc2f71898694b7fa41dd5be0471c917e113 (
plain) (
tree)
|
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML>
<HEAD>
<TITLE> [99s-extend] Cowboy: Maps instead of records for context variables
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Cowboy%3A%20Maps%20instead%20of%20records%20for%20context%0A%20variables&In-Reply-To=%3C5626401F.9050907%40ninenines.eu%3E">
<META NAME="robots" CONTENT="index,nofollow">
<style type="text/css">
pre {
white-space: pre-wrap; /* css-2.1, curent FF, Opera, Safari */
}
</style>
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="000557.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[99s-extend] Cowboy: Maps instead of records for context variables</H1>
<B>Loïc Hoguin</B>
<A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Cowboy%3A%20Maps%20instead%20of%20records%20for%20context%0A%20variables&In-Reply-To=%3C5626401F.9050907%40ninenines.eu%3E"
TITLE="[99s-extend] Cowboy: Maps instead of records for context variables">essen at ninenines.eu
</A><BR>
<I>Tue Oct 20 15:22:39 CEST 2015</I>
<P><UL>
<LI>Previous message: <A HREF="000557.html">[99s-extend] Cowboy: Maps instead of records for context variables
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#558">[ date ]</a>
<a href="thread.html#558">[ thread ]</a>
<a href="subject.html#558">[ subject ]</a>
<a href="author.html#558">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On 10/20/2015 03:19 PM, Ivan Uemlianin wrote:
><i> Dear All
</I>><i>
</I>><i> Would there be any reason against using a map instead of a record for
</I>><i> the context variable in a Cowboy REST resource?
</I>><i>
</I>><i> Quite often I have a few resources doing very similar things in their
</I>><i> callbacks, and I'd like to abstract out the similarities into a module -
</I>><i> but I don't want to share a record between modules.
</I>><i>
</I>><i> Maps seem to be a good fit, and I can't think of any downside
</I>><i> (performance hit should be tiny).
</I>><i>
</I>><i> Can anyone give me reasons to stick with records?
</I>
The only reason to use records is to keep typespecs information to
improve Dialyzer's error reporting.
Personally I have no problems going with just maps for all kinds of
states, even if they are in the same module. This is partly because I
rely a lot more on tests than on Dialyzer to tell me my program is wrong.
Cheers,
--
Loïc Hoguin
<A HREF="http://ninenines.eu">http://ninenines.eu</A>
Author of The Erlanger Playbook,
A book about software development using Erlang
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="000557.html">[99s-extend] Cowboy: Maps instead of records for context variables
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#558">[ date ]</a>
<a href="thread.html#558">[ thread ]</a>
<a href="subject.html#558">[ subject ]</a>
<a href="author.html#558">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://lists.ninenines.eu/listinfo/extend">More information about the Extend
mailing list</a><br>
</body></html>
|