agent_map

0.9.9

1.1.2 1.1.1 1.1.0 1.1.0-rc.1 1.1.0-rc.0 1.0.1 1.0.0 0.9.9

AgentMap can be seen as a stateful Map that parallelize operations made on different keys. Basically, it can be used as a cache, memoization, computational framework and, sometimes, as an alternative to GenServer.

HexDocs

Current section

Files

Jump to

Readme 8 Versions 0 Dependencies Dependants Files Activity

agent_map .formatter.exs

Raw

.formatter.exs

[
  inputs: ["mix.exs",
           "config/*.exs",
           "lib/agent_map/enumerable.ex",
           "lib/agent_map/server.ex",
           "lib/agent_map/request.ex",
           "lib/agent_map/transaction.ex",
           "lib/agent_map/worker.ex",
           "lib/agent_map.ex",
           "test/account.ex",
           "test/memo.ex",
          ]
]

Search filters

Type any of these into the search box. They can be combined with free text which searches package names and descriptions.

Operator	Description	Example
name:	Match package name. Supports * wildcards and repo/package form	name:phx* or name:hexpm/phoenix
description:	Full-text search of package descriptions	description:auth
depends:	Packages depending on a given package. Supports repo:package form	depends:ecto or depends:hexpm:ecto
build_tool:	Filter by build tool	build_tool:mix
updated_after:	Packages updated after an ISO8601 datetime	updated_after:2025-01-01T00:00:00Z
extra:	Match custom metadata (key,value). Nested keys are separated by commas	extra:license,MIT

Wrap values in double quotes to include spaces, e.g. name:"my package".