type_handler.cpp File Reference

#include <python-frontend/type/type_handler.h>
#include <clang-c-frontend/padding.h>
#include <python-frontend/json_utils.h>
#include <python-frontend/python_expr_builder.h>
#include <python-frontend/type/type_utils.h>
#include <python-frontend/python_converter.h>
#include <python-frontend/tuple/tuple_handler.h>
#include <python-frontend/type/python_typechecking.h>
#include <python-frontend/python_annotation/annotation_intrinsics.h>
#include <python-frontend/symbol_id.h>
#include <algorithm>
#include <util/arith/arith_tools.h>
#include <util/arith/bitvector.h>
#include <util/config/config.h>
#include <util/symtab/context.h>
#include <util/lang/c_types.h>
#include <util/message/message.h>
#include <util/irep/migrate.h>
#include <util/lang/python_types.h>
#include <irep2/irep2_utils.h>
#include <regex>

Include dependency graph for type_handler.cpp:

Functions
static void	throw_if_unmodelled_builtin_result (const std::string &ast_type)
	ast_type may be a call-result tag the intrinsic map invents for a builtin rather than a name from the source (iter -> "iterator", map -> "map", filter -> "filter").

Function Documentation

throw_if_unmodelled_builtin_result()

void throw_if_unmodelled_builtin_result ( const std::string & ast_type )

static

ast_type may be a call-result tag the intrinsic map invents for a builtin rather than a name from the source (iter -> "iterator", map -> "map", filter -> "filter").

No such type is modelled, so resolution lands here – but reporting a NameError blames a name the program never mentions. Name the builtin instead (esbmc/esbmc#7081). Returns if ast_type is not one.