main

LLeandro Osterafeat: add permissions to file open calls

58458b64创建于 2024年10月23日历史提交

文件	最后提交记录	最后更新时间
global	feat: clean up library namespace (#100) Gets rid of the global namespace pollution while preserving a single package. You can still use riot in your libraries just to get access to the stdlib. You can now depend only on the runtime if you really wish to (riot_runtime). Next step is the camel-casification of everything but pushing this now means refactoring a bunch of things that break downstream so we'll wait a few weeks. Should finally fix #19	1 年前
logger	feat: clean up library namespace (#100) Gets rid of the global namespace pollution while preserving a single package. You can still use riot in your libraries just to get access to the stdlib. You can now depend only on the runtime if you really wish to (riot_runtime). Next step is the camel-casification of everything but pushing this now means refactoring a bunch of things that break downstream so we'll wait a few weeks. Should finally fix #19	1 年前
SSL.ml	feat: clean up library namespace (#100) Gets rid of the global namespace pollution while preserving a single package. You can still use riot in your libraries just to get access to the stdlib. You can now depend only on the runtime if you really wish to (riot_runtime). Next step is the camel-casification of everything but pushing this now means refactoring a bunch of things that break downstream so we'll wait a few weeks. Should finally fix #19	1 年前
application.ml	feat: clean up library namespace (#100) Gets rid of the global namespace pollution while preserving a single package. You can still use riot in your libraries just to get access to the stdlib. You can now depend only on the runtime if you really wish to (riot_runtime). Next step is the camel-casification of everything but pushing this now means refactoring a bunch of things that break downstream so we'll wait a few weeks. Should finally fix #19	1 年前
crypto.ml	feat: clean up library namespace (#100) Gets rid of the global namespace pollution while preserving a single package. You can still use riot in your libraries just to get access to the stdlib. You can now depend only on the runtime if you really wish to (riot_runtime). Next step is the camel-casification of everything but pushing this now means refactoring a bunch of things that break downstream so we'll wait a few weeks. Should finally fix #19	1 年前
dune	feat: clean up library namespace (#100) Gets rid of the global namespace pollution while preserving a single package. You can still use riot in your libraries just to get access to the stdlib. You can now depend only on the runtime if you really wish to (riot_runtime). Next step is the camel-casification of everything but pushing this now means refactoring a bunch of things that break downstream so we'll wait a few weeks. Should finally fix #19	1 年前
dynamic_supervisor.ml	feat: clean up library namespace (#100) Gets rid of the global namespace pollution while preserving a single package. You can still use riot in your libraries just to get access to the stdlib. You can now depend only on the runtime if you really wish to (riot_runtime). Next step is the camel-casification of everything but pushing this now means refactoring a bunch of things that break downstream so we'll wait a few weeks. Should finally fix #19	1 年前
fd.ml	feat: clean up library namespace (#100) Gets rid of the global namespace pollution while preserving a single package. You can still use riot in your libraries just to get access to the stdlib. You can now depend only on the runtime if you really wish to (riot_runtime). Next step is the camel-casification of everything but pushing this now means refactoring a bunch of things that break downstream so we'll wait a few weeks. Should finally fix #19	1 年前
file.ml	feat: add permissions to file open calls	1 年前
gen_server.ml	feat: clean up library namespace (#100) Gets rid of the global namespace pollution while preserving a single package. You can still use riot in your libraries just to get access to the stdlib. You can now depend only on the runtime if you really wish to (riot_runtime). Next step is the camel-casification of everything but pushing this now means refactoring a bunch of things that break downstream so we'll wait a few weeks. Should finally fix #19	1 年前
hashmap.ml	feat: clean up library namespace (#100) Gets rid of the global namespace pollution while preserving a single package. You can still use riot in your libraries just to get access to the stdlib. You can now depend only on the runtime if you really wish to (riot_runtime). Next step is the camel-casification of everything but pushing this now means refactoring a bunch of things that break downstream so we'll wait a few weeks. Should finally fix #19	1 年前
key_value_store.ml	feat: clean up library namespace (#100) Gets rid of the global namespace pollution while preserving a single package. You can still use riot in your libraries just to get access to the stdlib. You can now depend only on the runtime if you really wish to (riot_runtime). Next step is the camel-casification of everything but pushing this now means refactoring a bunch of things that break downstream so we'll wait a few weeks. Should finally fix #19	1 年前
lib_io.ml	feat: clean up library namespace (#100) Gets rid of the global namespace pollution while preserving a single package. You can still use riot in your libraries just to get access to the stdlib. You can now depend only on the runtime if you really wish to (riot_runtime). Next step is the camel-casification of everything but pushing this now means refactoring a bunch of things that break downstream so we'll wait a few weeks. Should finally fix #19	1 年前
logger_app.ml	feat: clean up library namespace (#100) Gets rid of the global namespace pollution while preserving a single package. You can still use riot in your libraries just to get access to the stdlib. You can now depend only on the runtime if you really wish to (riot_runtime). Next step is the camel-casification of everything but pushing this now means refactoring a bunch of things that break downstream so we'll wait a few weeks. Should finally fix #19	1 年前
message.ml	feat: clean up library namespace (#100) Gets rid of the global namespace pollution while preserving a single package. You can still use riot in your libraries just to get access to the stdlib. You can now depend only on the runtime if you really wish to (riot_runtime). Next step is the camel-casification of everything but pushing this now means refactoring a bunch of things that break downstream so we'll wait a few weeks. Should finally fix #19	1 年前
net.ml	feat: clean up library namespace (#100) Gets rid of the global namespace pollution while preserving a single package. You can still use riot in your libraries just to get access to the stdlib. You can now depend only on the runtime if you really wish to (riot_runtime). Next step is the camel-casification of everything but pushing this now means refactoring a bunch of things that break downstream so we'll wait a few weeks. Should finally fix #19	1 年前
pid.ml	feat: clean up library namespace (#100) Gets rid of the global namespace pollution while preserving a single package. You can still use riot in your libraries just to get access to the stdlib. You can now depend only on the runtime if you really wish to (riot_runtime). Next step is the camel-casification of everything but pushing this now means refactoring a bunch of things that break downstream so we'll wait a few weeks. Should finally fix #19	1 年前
process.ml	feat: add permissions to file open calls	1 年前
queue.ml	feat: clean up library namespace (#100) Gets rid of the global namespace pollution while preserving a single package. You can still use riot in your libraries just to get access to the stdlib. You can now depend only on the runtime if you really wish to (riot_runtime). Next step is the camel-casification of everything but pushing this now means refactoring a bunch of things that break downstream so we'll wait a few weeks. Should finally fix #19	1 年前
ref.ml	feat: clean up library namespace (#100) Gets rid of the global namespace pollution while preserving a single package. You can still use riot in your libraries just to get access to the stdlib. You can now depend only on the runtime if you really wish to (riot_runtime). Next step is the camel-casification of everything but pushing this now means refactoring a bunch of things that break downstream so we'll wait a few weeks. Should finally fix #19	1 年前
riot_stdlib.ml	feat: clean up library namespace (#100) Gets rid of the global namespace pollution while preserving a single package. You can still use riot in your libraries just to get access to the stdlib. You can now depend only on the runtime if you really wish to (riot_runtime). Next step is the camel-casification of everything but pushing this now means refactoring a bunch of things that break downstream so we'll wait a few weeks. Should finally fix #19	1 年前
runtime_lib.ml	feat: clean up library namespace (#100) Gets rid of the global namespace pollution while preserving a single package. You can still use riot in your libraries just to get access to the stdlib. You can now depend only on the runtime if you really wish to (riot_runtime). Next step is the camel-casification of everything but pushing this now means refactoring a bunch of things that break downstream so we'll wait a few weeks. Should finally fix #19	1 年前
stream.ml	feat: clean up library namespace (#100) Gets rid of the global namespace pollution while preserving a single package. You can still use riot in your libraries just to get access to the stdlib. You can now depend only on the runtime if you really wish to (riot_runtime). Next step is the camel-casification of everything but pushing this now means refactoring a bunch of things that break downstream so we'll wait a few weeks. Should finally fix #19	1 年前
supervisor.ml	feat: clean up library namespace (#100) Gets rid of the global namespace pollution while preserving a single package. You can still use riot in your libraries just to get access to the stdlib. You can now depend only on the runtime if you really wish to (riot_runtime). Next step is the camel-casification of everything but pushing this now means refactoring a bunch of things that break downstream so we'll wait a few weeks. Should finally fix #19	1 年前
task.ml	feat: clean up library namespace (#100) Gets rid of the global namespace pollution while preserving a single package. You can still use riot in your libraries just to get access to the stdlib. You can now depend only on the runtime if you really wish to (riot_runtime). Next step is the camel-casification of everything but pushing this now means refactoring a bunch of things that break downstream so we'll wait a few weeks. Should finally fix #19	1 年前
telemetry_app.ml	feat: clean up library namespace (#100) Gets rid of the global namespace pollution while preserving a single package. You can still use riot in your libraries just to get access to the stdlib. You can now depend only on the runtime if you really wish to (riot_runtime). Next step is the camel-casification of everything but pushing this now means refactoring a bunch of things that break downstream so we'll wait a few weeks. Should finally fix #19	1 年前
timeout.ml	feat: clean up library namespace (#100) Gets rid of the global namespace pollution while preserving a single package. You can still use riot in your libraries just to get access to the stdlib. You can now depend only on the runtime if you really wish to (riot_runtime). Next step is the camel-casification of everything but pushing this now means refactoring a bunch of things that break downstream so we'll wait a few weeks. Should finally fix #19	1 年前